Re: [Bug #15805] reiserfs locking

[Frederic Weisbecker]

On Sat, Jul 10, 2010 at 09:06:50AM +0200, Ingo Molnar wrote:
> 
> * Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote:
> 
> > On Sat, Jul 10, 2010 at 02:33:24AM +0200, Rafael J. Wysocki wrote:
> > > This message has been generated automatically as a part of a report
> > > of regressions introduced between 2.6.33 and 2.6.34.
> > > 
> > > The following bug entry is on the current list of known regressions
> > > introduced between 2.6.33 and 2.6.34.  Please verify if it still should
> > > be listed and let the tracking team know (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15805
> > > Subject		: reiserfs locking
> > > Submitter	: Alexander Beregalov <a.beregalov@xxxxxxxxx>
> > > Date		: 2010-04-15 21:02 (86 days old)
> > > Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb@xxxxxxxxxxxxxx>
> > > References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2
> > > Handled-By	: Frederic Weisbecker <fweisbec@xxxxxxxxx>
> > 
> > 
> > It's a duplicate of 16334. Or rather 16334 is a duplicate of this
> > but the discussion about the issue was more developped in 16334.
> > 
> > Anyway this is not a regression (at least not recent) and the fix
> > from Al is in the vfs tree in the for-next branch on commit
> > 6c2bdaf089a3876226893fab00dd83596c465ad2
> > "Fix reiserfs_file_release()"
> 
> Since it's a reproducible deadlock maybe the fix should go upstream faster 
> than v2.6.36?
> 
> Thanks,
> 
> 	Ingo


May be yeah. Although the fix is not a naive trick and it changes a sensitive
piece of code.

Don't know what Al has planned with it.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/