The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Jiayuan Chen" <jiayuan.chen@linux.dev>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: linux-kernel@vger.kernel.org, mrpre@163.com,
	syzbot+adcaa842b762a1762e7d@syzkaller.appspotmail.com,
	syzbot+fab52e3459fa2f95df57@syzkaller.appspotmail.com,
	syzbot+0718f65353d72efaac1e@syzkaller.appspotmail.com,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Christian Brauner" <brauner@kernel.org>,
	"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	"Suren Baghdasaryan" <surenb@google.com>,
	"Wei Yang" <richard.weiyang@gmail.com>,
	"David Hildenbrand" <david@redhat.com>,
	"Al Viro" <viro@zeniv.linux.org.uk>,
	"Mateusz Guzik" <mjguzik@gmail.com>,
	"Oleg Nesterov" <oleg@redhat.com>,
	"Joel Granados" <joel.granados@kernel.org>,
	"Bill O'Donnell" <bodonnel@redhat.com>,
	"Darrick J. Wong" <djwong@kernel.org>,
	"Frederic Weisbecker" <frederic@kernel.org>
Subject: Re: [PATCH v2] pid: annotate data-races around pid_ns->pid_allocated
Date: Mon, 28 Apr 2025 08:30:24 +0000	[thread overview]
Message-ID: <7adb633683ed40587a379260857c7a48ce69638c@linux.dev> (raw)
In-Reply-To: <fo436hdqzkevk7jqszyprjjwehqge7rrqxz6gqbmgoqqsqwdxl@efe2r5jeouwl>

April 25, 2025 at 17:25, "Michal Koutný" <mkoutny@suse.com> wrote:

> 
> On Fri, Apr 25, 2025 at 01:58:14PM +0800, Jiayuan Chen <jiayuan.chen@linux.dev> wrote:
> 
> > 
> > Suppress syzbot reports by annotating these accesses using data_race().
> > 
> 
> Thanks for trying this approach.
> 
> scripts/checkpatch.pl has quite some remarks about the current form :-)
> 
> I mean, the data_race annotation should document why the race is
> 
> harmless. I only glanced over this so I can't tell myself whether it's a
> 
> bug or OK.
> 
> > 
> > Reported-by: syzbot+adcaa842b762a1762e7d@syzkaller.appspotmail.com
> > 
> >  Reported-by: syzbot+fab52e3459fa2f95df57@syzkaller.appspotmail.com
> > 
> >  Reported-by: syzbot+0718f65353d72efaac1e@syzkaller.appspotmail.com
> > 
> 
> How can I get to see full syzbot reports? (Stacktrace would be helpful,
> 
> I cannot resolve those as message-ids on (LK)ML.)
> 
> Thanks,
> 
> Michal
>

Hi Michal,

We can find such reports at https://syzkaller.appspot.com/upstream/s/kernel

  reply	other threads:[~2025-04-28  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25  5:58 [PATCH v2] pid: annotate data-races around pid_ns->pid_allocated Jiayuan Chen
2025-04-25  9:25 ` Michal Koutný
2025-04-28  8:30   ` Jiayuan Chen [this message]
2025-04-25 10:07 ` Oleg Nesterov

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=7adb633683ed40587a379260857c7a48ce69638c@linux.dev \
    --to=jiayuan.chen@linux.dev \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=bodonnel@redhat.com \
    --cc=brauner@kernel.org \
    --cc=david@redhat.com \
    --cc=djwong@kernel.org \
    --cc=frederic@kernel.org \
    --cc=joel.granados@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mjguzik@gmail.com \
    --cc=mkoutny@suse.com \
    --cc=mrpre@163.com \
    --cc=oleg@redhat.com \
    --cc=richard.weiyang@gmail.com \
    --cc=surenb@google.com \
    --cc=syzbot+0718f65353d72efaac1e@syzkaller.appspotmail.com \
    --cc=syzbot+adcaa842b762a1762e7d@syzkaller.appspotmail.com \
    --cc=syzbot+fab52e3459fa2f95df57@syzkaller.appspotmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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