Re: Bug#709947: closed by tytso@mit.edu (Theodore Y. Ts'o) (Bug#708307: fixed in e2fsprogs 1.42.8-1)
On Tue, Jun 25, 2013 at 08:54:50PM +0100, Adam D. Barratt wrote:
> On Tue, 2013-06-25 at 16:23 +0200, Peter Palfrader wrote:
> > On Fri, 21 Jun 2013, Debian Bug Tracking System wrote:
> > > * Work around Debian Bug #712530 (Closes: #708307)
> >
> > Thanks! Is that work-around suitable for a stable update as well?
>
> That's presumably this:
>
> --- e2fsprogs-1.42.5/debian/rules 2012-07-17 05:21:04.000000000 +0000
> +++ e2fsprogs-1.42.8/debian/rules 2013-06-16 22:39:06.000000000 +0000
> @@ -171,7 +171,9 @@
> USRLIB ?= /usr/lib
> endif
>
> -STD_CONF_FLAGS ?= --enable-symlink-install $(MULTIARCH_CONF)
> +BACKTRACE_CONF_FLAGS ?= $(shell if ${debdir}/scripts/test-backtrace ; then echo --disable-backtrace ; fi)
> +
> +STD_CONF_FLAGS ?= --enable-symlink-install $(MULTIARCH_CONF) $(BACKTRACE_CONF_FLAGS)
>
> plus the associated script? What's the practical impact of disabling the
> functionality?
It's a bit more than that. The full patch is here:
https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/commit/?h=maint&id=3df6014a3d216d19be7d2286de24e8ee106f18ad
It disables the ability to display a stack trace when e2fsck crashes,
which makes it easier for me to debug problems which only occur once
and where I can't get access to the file system which provoked the
fsck crash. Disabling reduces long term maintainability and RAS, but
doesn't cause any other missing functionality to the user.
- Ted
Reply to: