All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Dave Chinner <david@fromorbit.com>
Subject: Re: linux-next: Tree for July 7
Date: Wed, 14 Jul 2010 17:27:41 -0700	[thread overview]
Message-ID: <20100714172741.f520b7a3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100715094513.8941fa25.sfr@canb.auug.org.au>

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

> Hi Andrew, Al,
> 
> On Wed, 14 Jul 2010 15:20:42 -0700 Andrew Morton <akpm@linux-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?

  reply	other threads:[~2010-07-15  0:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07  6:55 linux-next: Tree for July 7 Stephen Rothwell
2010-07-07 23:20 ` Andrew Morton
2010-07-07 23:41 ` [PATCH -next] IR: jvc-decoder needs BITREVERSE Randy Dunlap
2010-07-08  0:21 ` linux-next: Tree for July 7 Andrew Morton
2010-07-14 22:20   ` Andrew Morton
2010-07-14 22:20     ` Andrew Morton
2010-07-14 23:45     ` Stephen Rothwell
2010-07-15  0:27       ` Andrew Morton [this message]
2010-07-15  0:46         ` Dave Chinner
2010-07-15  0:53           ` Andrew Morton
2010-07-15  2:12             ` Dave Chinner
2010-07-15  7:18               ` Dave Chinner
  -- strict thread matches above, loose matches on Subject: below --
2011-07-07  7:25 Stephen Rothwell
2009-07-07  6:34 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100714172741.f520b7a3.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.