From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Jann Horn <jannh@google.com>
Cc: syzkaller <syzkaller@googlegroups.com>,
syzbot <syzbot+c2e5712cbb14c95d4847@syzkaller.appspotmail.com>,
Liam.Howlett@oracle.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: [syzbot] [mm?] KCSAN: data-race in mprotect_fixup / try_to_migrate_one
Date: Wed, 5 Feb 2025 15:34:45 +0000 [thread overview]
Message-ID: <74308437-2684-46d3-a2c1-c55ed4dde042@lucifer.local> (raw)
In-Reply-To: <CAG48ez0DYnDKikFUrPQOppsW_-aa2_hcoyOcRJeCMRrEm6GVTA@mail.gmail.com>
On Wed, Feb 05, 2025 at 04:14:03PM +0100, Jann Horn wrote:
> On Wed, Feb 5, 2025 at 4:07 PM Lorenzo Stoakes
> <lorenzo.stoakes@oracle.com> wrote:
> > On Wed, Feb 05, 2025 at 03:41:20AM -0800, syzbot wrote:
> > > read to 0xffff888114b41700 of 8 bytes by task 6418 on cpu 0:
> > > try_to_migrate_one+0xb5a/0x12e0 mm/rmap.c:2321
> >
> > Be super nice if these reports could show the line of code!
> >
> > It's:
> >
> > if (vma->vm_flags & VM_LOCKED)
>
> fwiw if you follow the "dashboard link" in the bug report, you'll get
> a version of this where the source locations are clickable links to
> git.kernel.org at the right commit.
>
> Also note the "syzbot engineers can be reached at
> syzkaller@googlegroups.com" at the bottom of the message.
But but but... I like shouting into the void! :P
Anyway I see that they're cc'd and sometimes reply, this was more a
meandering thought if somebody happened to notice rather than urgent. A
'nice to have' if you will...
prev parent reply other threads:[~2025-02-05 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 11:41 syzbot
2025-02-05 15:00 ` Jann Horn
2025-02-05 15:11 ` Lorenzo Stoakes
2025-02-05 15:14 ` Jann Horn
2025-02-05 15:46 ` Marco Elver
2025-02-05 15:51 ` Lorenzo Stoakes
2025-02-05 16:25 ` Marco Elver
2025-02-05 18:56 ` Liam R. Howlett
2025-02-05 18:59 ` Lorenzo Stoakes
2025-02-05 15:47 ` Liam R. Howlett
2025-02-05 15:52 ` Jann Horn
2025-02-05 15:07 ` Lorenzo Stoakes
2025-02-05 15:14 ` Jann Horn
2025-02-05 15:34 ` Lorenzo Stoakes [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=74308437-2684-46d3-a2c1-c55ed4dde042@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+c2e5712cbb14c95d4847@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@googlegroups.com \
--cc=vbabka@suse.cz \
/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