From: Christoph Hellwig <hch@lst.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] Block fix for 5.12 final
Date: Sat, 24 Apr 2021 08:52:48 +0200 [thread overview]
Message-ID: <20210424065248.GA9706@lst.de> (raw)
In-Reply-To: <CAHk-=wi5otGvBvWGx-XC=es88Xghe1TNFEYg_ZwoiZBzRvGeRA@mail.gmail.com>
On Fri, Apr 23, 2021 at 02:54:36PM -0700, Linus Torvalds wrote:
> On Fri, Apr 23, 2021 at 2:06 PM Jens Axboe <axboe@kernel.dk> wrote:
> >
> > A single fix for a behavioral regression in this series, when re-reading
> > the partition table with partitions open.
>
> Hmm. The fact that it's no longer calling blk_drop_partitions() didn't
> just mean that the check for "bdev->bd_part_count" was lost (now
> re-instated).
It still calls blk_drop_partitions:
blkdev_reread_part
-> blkdev_get_by_dev
-> __blkdev_get
-> bdev_disk_changed
-> blk_drop_partitions
The difference is that before blkdev_reread_part called
bdev_disk_changed directly. We now do it through blkdev_get to hook
into the driver. But __blkdev_get ignores the return value from
bdev_disk_changed.
> It also seems to mean that blkdev_reread_part() no longer does the
>
> sync_blockdev(bdev);
> invalidate_bdev(bdev);
>
> to write back and invalidate any caches.
>
> Are we sure cache writeback/invalidate isn't needed? Or does it get
> done some other place?
It is still in place. But given how our cache coherency works not
actually needed anyway, but peeling that onion will take a while.
next prev parent reply other threads:[~2021-04-24 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 21:06 [GIT PULL] Block fix for 5.12 final Jens Axboe
2021-04-23 21:54 ` Linus Torvalds
2021-04-23 23:18 ` Jens Axboe
2021-04-24 6:52 ` Christoph Hellwig [this message]
2021-04-23 21:55 ` pr-tracker-bot
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=20210424065248.GA9706@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=torvalds@linux-foundation.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