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] [day] [month] [year] [list]
Message-ID: <026e2cd5-84fa-4f14-83cb-d6b49053b7ae@lucifer.local>
Date: Sun, 18 Jan 2026 12:31:47 +0000
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Deepanshu Kartikey <kartikey406@...il.com>
Cc: akpm@...ux-foundation.org, david@...nel.org, riel@...riel.com,
        Liam.Howlett@...cle.com, vbabka@...e.cz, harry.yoo@...cle.com,
        jannh@...gle.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        syzbot+c27fa543e10a45d4e149@...kaller.appspotmail.com
Subject: Re: [PATCH] mm/rmap: fix unlink_anon_vmas() handling of error case
 from anon_vma_fork

On Sun, Jan 18, 2026 at 05:54:35PM +0530, Deepanshu Kartikey wrote:
> Hi Lorenzo,
>
> Yes, I used  AI for commit message drafting and to help
> articulate the technical explanation. The bug analysis, code fix,
> and testing are mine.
>
> I'll send v2 with proper acknowledgment. Thanks for catching this.

No, please don't - As I told you in the other reply, this patch is not
acceptable.

When a patch is not upstream the appropriate thing to do is to comment on
the series.

We rebase development patches before they go upstream, so it just makes no
sense.

In addition this patch is not upstreamble as-is. You are getting at the
issue, but you're effectively undermining what my series does with this
proposal.

So while I appreciate the report, unfortunately this is not a patch we can
do anything with.

>
> Deepanshu

Thanks, Lorenzo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ