linux-kernel - Re: linux-next: Tree for July 7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100714172741.f520b7a3.akpm@linux-foundation.org>
Date:	Wed, 14 Jul 2010 17:27:41 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
	Al Viro <viro@...iv.linux.org.uk>,
	Dave Chinner <david@...morbit.com>
Subject: Re: linux-next: Tree for July 7

On Thu, 15 Jul 2010 09:45:13 +1000
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Andrew, Al,
> 
> On Wed, 14 Jul 2010 15:20:42 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > Bug is still there.  Reverting ""Make ->drop_inode() just return
> > whether inode needs to be dropped" makes it go away.
> > 
> > Al, please don't just dump crap in linux-next and then ignore bug reports. 
> > People are trying to get work done here.
> 
> I will revert that commit in linux-next today if it is still there (and
> not fixed).

Reverting the patch didn't help - the patch moved the BUG_ON() from
generic_delete_inode() into __iput_final().  With the patch reverted
the kernel still goes BUG over the same test in generic_delete_inode().

It could be that the bug was caused by fs-writeback.c changes.  David,
do you have time to take a look at this?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/