All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Randy Dunlap <rdunlap@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: Fri, 14 Jan 2022 00:30:37 +0000	[thread overview]
Message-ID: <YeDELXPXWuM1qZc/@casper.infradead.org> (raw)
In-Reply-To: <24d83e9c-a4d5-176b-1ff3-909d0ad56302@infradead.org>

On Thu, Jan 13, 2022 at 01:26:48PM -0800, Randy Dunlap wrote:
> 
> 
> 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.  It's now at
https://git.infradead.org/users/willy/pagecache.git/shortlog/refs/heads/for-next
so it'll be part of the next linux-next.

      reply	other threads:[~2022-01-14  0:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  4:22 linux-next: Tree for Jan 13 Stephen Rothwell
2022-01-13 20:12 ` linux-next: Tree for Jan 13 (UBSAN: invalid-load in ../mm/swap.c:996:11) Randy Dunlap
2022-01-13 20:47   ` Matthew Wilcox
2022-01-13 21:26     ` Randy Dunlap
2022-01-14  0:30       ` Matthew Wilcox [this message]

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=YeDELXPXWuM1qZc/@casper.infradead.org \
    --to=willy@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=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.