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:   Wed, 2 Dec 2020 20:06:01 +0100
From:   Greg Kroah-Hartman <>
To:     Miklos Szeredi <>
Cc:     David Howells <>,
        Ira Weiny <>,
        Eric Sandeen <>,
        Linus Torvalds <>,
        Miklos Szeredi <>,,
        linux-man <>,, xfs <>,, Xiaoli Feng <>
Subject: Re: [PATCH V2] uapi: fix statx attribute value overlap for DAX &

On Wed, Dec 02, 2020 at 06:41:43PM +0100, Miklos Szeredi wrote:
> On Wed, Dec 2, 2020 at 5:24 PM David Howells <> wrote:
> >
> > Miklos Szeredi <> wrote:
> >
> > > Stable cc also?
> > >
> > > Cc: <> # 5.8
> >
> > That seems to be unnecessary, provided there's a Fixes: tag.
> Is it?
> Fixes: means it fixes a patch, Cc: stable means it needs to be
> included in stable kernels.  The two are not necessarily the same.
> Greg?

You are correct.  cc: stable, as is documented in
ensures that the patch will get merged into the stable tree.

Fixes: is independent of it.  It's great to have for stable patches so
that I know how far back to backport patches.

We do scan all commits for Fixes: tags that do not have cc: stable, and
try to pick them up when we can and have the time to do so.  But it's
not guaranteed at all that this will happen.

I don't know why people keep getting confused about this, we don't
document the "Fixes: means it goes to stable" anywhere...


greg k-h

Powered by blists - more mailing lists