From: Ritesh Harjani <riteshh@linux.ibm.com>
To: Christoph Hellwig <hch@infradead.org>, tytso@mit.edu
Cc: linux-ext4@vger.kernel.org, jack@suse.com,
Hillf Danton <hdanton@sina.com>,
linux-fsdevel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
syzbot+82f324bb69744c5f6969@syzkaller.appspotmail.com
Subject: Re: [PATCHv2 1/1] ext4: mballoc: Use this_cpu_read instead of this_cpu_ptr
Date: Wed, 10 Jun 2020 12:04:31 +0530 [thread overview]
Message-ID: <20200610063432.354E411C04A@d06av25.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20200610062538.GA24975@infradead.org>
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@lst.de>
>
Thanks
-ritesh
next prev parent reply other threads:[~2020-06-10 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 10:53 [PATCHv2 1/1] ext4: mballoc: Use this_cpu_read instead of this_cpu_ptr Ritesh Harjani
2020-06-10 6:25 ` Christoph Hellwig
2020-06-10 6:34 ` Ritesh Harjani [this message]
2020-06-11 15:03 ` Theodore Y. Ts'o
[not found] <20200609123716.16888-1-hdanton@sina.com>
2020-06-10 2:06 ` Ritesh Harjani
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=20200610063432.354E411C04A@d06av25.portsmouth.uk.ibm.com \
--to=riteshh@linux.ibm.com \
--cc=bp@alien8.de \
--cc=hch@infradead.org \
--cc=hdanton@sina.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=syzbot+82f324bb69744c5f6969@syzkaller.appspotmail.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).