[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPhsuW7-Kq_bFpXtDUpiWtmBTFajewv=Uv4_GZR4zcoB9m1dBg@mail.gmail.com>
Date: Thu, 28 Sep 2023 08:54:02 -0700
From: Song Liu <song@...nel.org>
To: Yu Kuai <yukuai1@...weicloud.com>
Cc: xni@...hat.com, agk@...hat.com, snitzer@...nel.org,
dm-devel@...hat.com, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org, yukuai3@...wei.com,
yi.zhang@...wei.com, yangerkun@...wei.com
Subject: Re: [PATCH -next v3 01/25] md: use READ_ONCE/WRITE_ONCE for
'suspend_lo' and 'suspend_hi'
On Wed, Sep 27, 2023 at 11:22 PM Yu Kuai <yukuai1@...weicloud.com> wrote:
>
> From: Yu Kuai <yukuai3@...wei.com>
>
> Because reading 'suspend_lo' and 'suspend_hi' from md_handle_request()
> is not protected, use READ_ONCE/WRITE_ONCE to prevent reading abnormal
> value.
I rephrase this a bit:
Protect 'suspend_lo' and 'suspend_hi' with READ_ONCE/WRITE_ONCE to prevent
reading abnormal values.
Thanks,
Song
Powered by blists - more mailing lists