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  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]
Date:   Sat, 2 Oct 2021 18:15:58 +0100
From:   Matthew Wilcox <>
To:     Eric Dumazet <>
Cc:     Andrew Morton <>,
        Eric Dumazet <>,
        linux-kernel <>,
        linux-mm <>,
        syzbot <>,
        "Huang, Ying" <>, Mel Gorman <>
Subject: Re: [PATCH v2] mm/mempolicy: do not allow illegal

On Fri, Oct 01, 2021 at 04:37:40PM -0700, Eric Dumazet wrote:
> > > Issue came with commit bda420b98505 ("numa balancing: migrate on
> > > fault among multiple bound nodes")
> >
> > No cc:stable?  What's the worst-case user-visible impact here?
> I added the more precise tag  :  Fixes: bda420b98505 ("numa balancing:
> migrate on fault among multiple bound nodes")
> I only put Fixes: tag, so that stable teams can use their automation just fine.
> worst-case impact, I am not sure if any application ever used this
> undocumented combinations of flags ?
> Also, it is generally advised that accessing garbage values has
> undocumented behavior.
> A host could for example crash (it certainly does with KMSAN)

mm has special stable rules; fixes only get backported if explicitly
requested instead of automatically like most of the rest of the kernel.

Powered by blists - more mailing lists