From: NeilBrown <neilb@suse.de>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Christoph Hellwig <hch@lst.de>, Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: md related oops triggered in bdev_inode_switch_bdi
Date: Thu, 1 Sep 2011 15:49:36 +1000 [thread overview]
Message-ID: <20110901154936.26e35821@notabene.brown> (raw)
In-Reply-To: <20110901033056.GA22050@localhost>
On Thu, 1 Sep 2011 11:30:56 +0800 Wu Fengguang <fengguang.wu@intel.com> wrote:
> Hi Neil,
>
> > Subject: [PATCH] Avoid dereferencing a 'request_queue' after last close.
>
> Reviewed-by: Wu Fengguang <fengguang.wu@intel.com>
Thanks.
>
> with comments below.
>
> > --- a/fs/block_dev.c
> > +++ b/fs/block_dev.c
> > @@ -1430,6 +1430,12 @@ static int __blkdev_put(struct block_device *bdev, fmode_t mode, int for_part)
> > sync_blockdev(bdev);
> > kill_bdev(bdev);
> > }
> > + if (!bdev->bd_openers)
> > + /* ->release can cause the old bdi to disappear,
> > + * so must switch it out first
> > + */
> > + bdev_inode_switch_bdi(bdev->bd_inode,
> > + &default_backing_dev_info);
> > if (bdev->bd_contains == bdev) {
> > if (disk->fops->release)
> > ret = disk->fops->release(disk, mode);
>
> The bdev_inode_switch_bdi() call can be further moved into the
> previous if block, like this:
>
> if (!--bdev->bd_openers) {
> WARN_ON_ONCE(bdev->bd_holders);
> sync_blockdev(bdev);
> kill_bdev(bdev);
> +
> + /* ->release can cause the old bdi to disappear,
> + * so must switch it out first
> + */
> + bdev_inode_switch_bdi(bdev->bd_inode,
> + &default_backing_dev_info);
> }
Yes, and obvious improvement now that you have pointed it out - thanks.
>
> Then it's obvious that kill_bdev() will truncate all inode pages
> and there won't be further interactions with dirty writes.
>
> Although there are dozens of disk->fops->release functions, however
> it's very unlikely they need to access some inode on top of the disk
> (which is illogical thing).
>
> So I don't see any problems. It makes sense to push it to next for
> broader test ASAP. Will you do it, or me?
I've just push it into my for-next. If I heard nothing else by mid next week
I'll push it to Linus
Thanks,
NeilBrown
>
> Thanks,
> Fengguang
next prev parent reply other threads:[~2011-09-01 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 6:22 md related oops triggered in bdev_inode_switch_bdi NeilBrown
2011-09-01 3:30 ` Wu Fengguang
2011-09-01 5:49 ` NeilBrown [this message]
2011-09-09 8:56 ` Lin Ming
2011-09-11 7:01 ` Sitsofe Wheeler
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=20110901154936.26e35821@notabene.brown \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hch@lst.de \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox