On Sat, Nov 19, 2016 at 11:01:31AM +0100, Santiago Vila wrote:
> > No, it's not dangerous. It's also fixed in 1.42.13:
> >
> > commit fecb231f6fc83cf4b4ddf7ec34ace3723803a499
> > Author: Darrick J. Wong <darrick.w...@oracle.com>
> > Date: Fri Nov 7 21:26:14 2014 -0500
> >
> > dumpe2fs: don't crash when the user provides no block device argument
> >
> > If the user doesn't provide any arguments, the guard fails to run and
> > the whole thing segfaults on ext2fs_open2(). Don't do that.
> >
> > Signed-off-by: Darrick J. Wong <darrick.w...@oracle.com>
> > Signed-off-by: Theodore Ts'o <ty...@mit.edu>
> >
> >
> > If you really care, feel free to grab the e2fsprogs from debian-bacports.
>
> Well, yes, I do care, but backports is for new features, not to fix bugs like
> this.
>
> Would not be possible to fix this in a point release?
Why do you care? It's an extremely minor bug, and it's really not
worth the effort to fix things for just a really minor bugfix like
this. Given that e2fsprogs is used in the installer, it means that if
I push a fix, the installer would have to be respun, etc. So it's a
lot of work (for people beyond just me) for very little gain.
- Ted
