From: Randy Dunlap <rdunlap@infradead.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Jan 13 (UBSAN: invalid-load in ../mm/swap.c:996:11)
Date: Thu, 13 Jan 2022 13:26:48 -0800 [thread overview]
Message-ID: <24d83e9c-a4d5-176b-1ff3-909d0ad56302@infradead.org> (raw)
In-Reply-To: <YeCP8Kh+4y7NR1K+@casper.infradead.org>
On 1/13/22 12:47, Matthew Wilcox wrote:
> On Thu, Jan 13, 2022 at 12:12:52PM -0800, Randy Dunlap wrote:
>> [ 1.561983] UBSAN: invalid-load in ../mm/swap.c:996:11
>> [ 1.561986] load of value 221 is not a valid value for type '_Bool'
>
> Ooh. This one's mine. Randy, does it repeat easily? This should
> fix it:
Yes, 100% of the time (for N = 3).
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Fixed 100% of the time (for N = 3).
Thanks.
> diff --git a/include/linux/pagevec.h b/include/linux/pagevec.h
> index dda8d5868c81..67b1246f136b 100644
> --- a/include/linux/pagevec.h
> +++ b/include/linux/pagevec.h
> @@ -111,6 +111,7 @@ static_assert(offsetof(struct pagevec, pages) ==
> static inline void folio_batch_init(struct folio_batch *fbatch)
> {
> fbatch->nr = 0;
> + fbatch->percpu_pvec_drained = false;
> }
>
> static inline unsigned int folio_batch_count(struct folio_batch *fbatch)
>
--
~Randy
next prev parent reply other threads:[~2022-01-13 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220113152247.3f7c6c49@canb.auug.org.au>
2022-01-13 20:12 ` Randy Dunlap
2022-01-13 20:47 ` Matthew Wilcox
2022-01-13 21:26 ` Randy Dunlap [this message]
2022-01-14 0:30 ` Matthew Wilcox
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=24d83e9c-a4d5-176b-1ff3-909d0ad56302@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=willy@infradead.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