From: Ming Lei <ming.lei@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Yu Kuai <yukuai1@huaweicloud.com>,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yukuai3@huawei.com,
yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH v3 2/3] block: introduce new field bd_flags in block_device
Date: Thu, 23 Nov 2023 10:19:30 +0800 [thread overview]
Message-ID: <ZV62svvu5MSUGoPD@fedora> (raw)
In-Reply-To: <ZV34d/hI12pKFUzj@infradead.org>
On Wed, Nov 22, 2023 at 04:47:51AM -0800, Christoph Hellwig wrote:
> On Wed, Nov 22, 2023 at 04:19:40PM +0800, Ming Lei wrote:
> > On Tue, Nov 21, 2023 at 11:53:17PM -0800, Christoph Hellwig wrote:
> > > On Wed, Nov 22, 2023 at 03:45:24PM +0800, Ming Lei wrote:
> > > > All the existed 'bool' flags are not atomic RW, so I think it isn't
> > > > necessary to define 'bd_flags' as 'unsigned long' for replacing them.
> > >
> > > So because the old code wasn't correct we'll never bother? The new
> > > flag and the new placement certainly make this more critical as well.
> >
> > Can you explain why the old code was wrong?
> >
> > 1) ->bd_read_only and ->bd_make_it_fail
> >
> > - set from userspace interface(ioctl or sysfs)
> > - check in IO code path
> >
> > so changing it into atomic bit doesn't make difference from user
> > viewpoint.
>
> >
> > 2) ->bd_write_holder
> >
> > disk->open_mutex is held for read & write this flag
> >
> > 3) ->bd_has_submit_bio
> >
> > This flag is setup as oneshot before adding disk, and check in FS io code
> > path.
>
> On architectures that can't do byte-level atomics all three can corrupt
> each other
Yeah, C/C++ doesn't provide such guarantee, but many modern ARCHs [1]
guarantees that RW on naturally aligned type is atomic.
I verified the point on x86/arm64/ppc64le by the following code, and
all three STOREs are done in single instruction.
struct data {
int b;
char a;
char a2;
char a3;
char a4;
} __attribute__((aligned(8)));
void atomic_test()
{
struct data d;
d.b = 1;
d.a = 2;
d.a3 = 3;
printf("%d %d %d\n", d.b, d.a, d.a3);
}
[1] https://preshing.com/20130618/atomic-vs-non-atomic-operations/
> and even worse bd_partno. Granted that is only alpha these
> days IIRC, but it's still buggy.
bd_has_submit_bio and bd_partno can be thought as read only, and the
two can be corrupted?
bd_dev may have similar trouble with bd_partno for ARCHs which don't
provide atomic RW on naturally aligned int.
Thanks,
Ming
next prev parent reply other threads:[~2023-11-23 2:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 10:31 [PATCH v3 0/3] block: warn once for each partition in bio_check_ro() Yu Kuai
2023-11-22 10:31 ` [PATCH v3 1/3] block: move .bd_inode into 1st cacheline of block_device Yu Kuai
2023-11-22 7:23 ` Christoph Hellwig
2023-11-22 11:17 ` Yu Kuai
2023-11-22 10:31 ` [PATCH v3 2/3] block: introduce new field bd_flags in block_device Yu Kuai
2023-11-22 3:30 ` Ming Lei
2023-11-22 6:15 ` Yu Kuai
2023-11-22 3:52 ` Michael Kelley
2023-11-22 7:06 ` Yu Kuai
2023-11-22 7:28 ` Christoph Hellwig
2023-11-22 7:45 ` Ming Lei
2023-11-22 7:53 ` Christoph Hellwig
2023-11-22 8:19 ` Ming Lei
2023-11-22 12:47 ` Christoph Hellwig
2023-11-23 2:19 ` Ming Lei [this message]
2023-11-22 10:31 ` [PATCH v3 3/3] block: warn once for each partition in bio_check_ro() Yu Kuai
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=ZV62svvu5MSUGoPD@fedora \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.com \
/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