[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200610063432.354E411C04A@d06av25.portsmouth.uk.ibm.com>
Date: Wed, 10 Jun 2020 12:04:31 +0530
From: Ritesh Harjani <riteshh@...ux.ibm.com>
To: Christoph Hellwig <hch@...radead.org>, tytso@....edu
Cc: linux-ext4@...r.kernel.org, jack@...e.com,
Hillf Danton <hdanton@...a.com>, linux-fsdevel@...r.kernel.org,
Borislav Petkov <bp@...en8.de>,
Marek Szyprowski <m.szyprowski@...sung.com>,
syzbot+82f324bb69744c5f6969@...kaller.appspotmail.com
Subject: Re: [PATCHv2 1/1] ext4: mballoc: Use this_cpu_read instead of
this_cpu_ptr
On 6/10/20 11:55 AM, Christoph Hellwig wrote:
> On Tue, Jun 09, 2020 at 04:23:10PM +0530, Ritesh Harjani wrote:
>> Simplify reading a seq variable by directly using this_cpu_read API
>> instead of doing this_cpu_ptr and then dereferencing it.
>>
>> This also avoid the below kernel BUG: which happens when
>> CONFIG_DEBUG_PREEMPT is enabled
>
> I see this warning all the time with ext4 using tests VMs, so lets get
> this fixed ASAP before -rc1:
Couldn't agree more.
>
> Reviewed-by: Christoph Hellwig <hch@....de>
>
Thanks
-ritesh
Powered by blists - more mailing lists