From: Muhammad Haris Awan <m.harisawan@icloud.com>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: David Hildenbrand <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Kees Cook <kees@kernel.org>, Liam R. Howlett <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] fork: mark memcpy() in dup_mm() with data_race()
Date: Tue, 17 Nov 2026 19:26:08 +0500 [thread overview]
Message-ID: <179492556819.269625.4305215206796797018@icloud.com> (raw)
In-Reply-To: <avxPvfV4NxKL58ZR@gremlin>
I accept the technical feedback. Silencing KCSAN on the whole dup_mm()
memcpy is too broad so I'm dropping this patch.
To be honest, I used AI to help draft the messages and I should have
mentioned that. I picked up this open syzbot bug because I genuinely
want to contribute to Linux and open source, and I chose a rare edge
case because I thought no one else would pick it.
A technical NACK is totally fine and I appreciate the review, but calling
a new contributor's attempt "slop" isn't really needed to say the fix
isn't good.
With respect,
Haris
next prev parent reply other threads:[~2026-11-17 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 5:59 Muhammad Haris Awan
2026-11-17 8:59 ` David Hildenbrand (Arm)
2026-11-17 10:24 ` Muhammad Haris Awan
2026-11-17 10:54 ` David Hildenbrand (Arm)
2026-11-17 13:02 ` Lorenzo Stoakes (ARM)
2026-11-17 14:26 ` Muhammad Haris Awan [this message]
2026-11-17 12:58 ` Lorenzo Stoakes (ARM)
2026-11-17 16:23 ` Bradley Morgan
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=179492556819.269625.4305215206796797018@icloud.com \
--to=m.harisawan@icloud.com \
--cc=akpm@linux-foundation.org \
--cc=bsegall@google.com \
--cc=david@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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
all inboxes | Powered by JetHome®