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: <CAJuCfpGZVrFZnBp=gO5kLY-Ky0jZE=L5Kv-qv2gW3FeQTt0s9g@mail.gmail.com>
Date: Thu, 15 Jan 2026 14:56:25 -0800
From: Suren Baghdasaryan <surenb@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: ranxiaokai627@....com, kent.overstreet@...ux.dev, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org, ran.xiaokai@....com.cn
Subject: Re: [PATCH v2] alloc_tag: fix rw permission issue when handling boot parameter

On Thu, Jan 15, 2026 at 2:12 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Wed, 14 Jan 2026 20:58:52 -0800 Suren Baghdasaryan <surenb@...gle.com> wrote:
>
> > > > Suggested-by: Suren Baghdasaryan <surenb@...gle.com>
> > > > Acked-by: Suren Baghdasaryan <surenb@...gle.com>
> > > > Signed-off-by: Ran Xiaokai <ran.xiaokai@....com.cn>
> > >
> > > Should we backport it?
> >
> > I'm not sure a single boot time warning produced only in debug mode
> > warrants backporting. Do you think we should do it anyway?
>
> Not if you don't ;)  Just checking...

The code around this recently changed and the patch will have to be
backported. I'm still happy to do that if someone asks for it but I
don't think it's critical enough to be proactive :)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ