linux-kernel - Re: [PATCH v4] mm, kasan, kmsan: copy_from/to_kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20241009143911.3c394e1bc598f59ce764a67c@linux-foundation.org>
Date: Wed, 9 Oct 2024 14:39:11 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Sabyrzhan Tasbolatov <snovitoll@...il.com>
Cc: Marco Elver <elver@...gle.com>, andreyknvl@...il.com,
 bpf@...r.kernel.org, dvyukov@...gle.com, glider@...gle.com,
 kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org,
 linux-mm@...ck.org, ryabinin.a.a@...il.com,
 syzbot+61123a5daeb9f7454599@...kaller.appspotmail.com,
 vincenzo.frascino@....com
Subject: Re: [PATCH v4] mm, kasan, kmsan: copy_from/to_kernel_nofault

On Wed, 9 Oct 2024 00:42:25 +0500 Sabyrzhan Tasbolatov <snovitoll@...il.com> wrote:

> > > v4:
> > > - replaced Suggested-By with Reviewed-By: Marco Elver
> >
> > For future reference: No need to send v+1 just for this tag. Usually
> > maintainers pick up tags from the last round without the original
> > author having to send out a v+1 with the tags. Of course, if you make
> > other corrections and need to send a v+1, then it is appropriate to
> > collect tags where those tags would remain valid (such as on unchanged
> > patches part of the series, or for simpler corrections).
> 
> Thanks! Will do it next time.
> 
> Please advise if Andrew should need to be notified in the separate cover letter
> to remove the prev. merged  to -mm tree patch and use this v4:
> https://lore.kernel.org/all/20241008020150.4795AC4CEC6@smtp.kernel.org/

I've updated v3's changelog, thanks.

I kept Marco's Suggested-by:, as that's still relevant even with the
Reviewed-by:.