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:   Thu, 9 Sep 2021 16:11:09 -0700
From:   Andrew Morton <>
To:     Kees Cook <>
Cc:     kernel test robot <>,
        Matt Porter <>,
        Alexandre Bounine <>,
        Jing Xiangfeng <>,
        Ira Weiny <>,
        John Hubbard <>,
        Souptick Joarder <>,
        "Gustavo A . R . Silva" <>,
        Dan Carpenter <>,,
Subject: Re: [PATCH] rapidio: Avoid bogus __alloc_size warning

On Thu, 9 Sep 2021 15:51:23 -0700 Kees Cook <> wrote:

> > That's an "error", not a warning.  Or is this thanks to the new -Werror?
> This is a "regular" error (__bad_copy_to() uses __compiletime_error()).
> > Either way, I'm inclined to cc:stable on this, because use of gcc-9 on
> > older kernels will be a common thing down the ages.
> > 
> > If it's really an "error" on non-Werror kernels then definitely cc:stable.
> I would expect that as only being needed if __alloc_size was backported
> to -stable, which seems unlikely.

Ah.  Changelog didn't tell me that it's an __alloc_size thing.

What's the status of the __alloc_size() patchset, btw?

Powered by blists - more mailing lists