linux-kernel - Re: linux-next: Fixes tags needs some work in the selinux tree

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: <CAHC9VhSsFzMxBdJHYOgq4X-PwQWLX2+UP5_T_U38mYd1_BeSHw@mail.gmail.com>
Date:   Thu, 14 Oct 2021 20:51:38 -0400
From:   Paul Moore <paul@...l-moore.com>
To:     Todd Kjos <tkjos@...gle.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tags needs some work in the selinux tree

On Thu, Oct 14, 2021 at 8:21 PM Todd Kjos <tkjos@...gle.com> wrote:
> On Thu, Oct 14, 2021 at 3:53 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Hi all,
> >
> > In commit
> >
> >   fef994d85ac9 ("binder: use cred instead of task for getsecid")
> >
> > Fixes tag
> >
> >   Fixes: ec74136ded79 ("binder: create node flag to request sender's
> >
> > has these problem(s):
> >
> >   - Subject has leading but no trailing parentheses
> >   - Subject has leading but no trailing quotes
> >
> > In commit
> >
> >   d1c927fb8b52 ("binder: use cred instead of task for selinux checks")
> >
> > Fixes tag
> >
> >   Fixes: 79af73079d75 ("Add security hooks to binder and implement the
> >
> > has these problem(s):
> >
> >   - Subject has leading but no trailing parentheses
> >   - Subject has leading but no trailing quotes
> >
> > Please do not split Fixes tags over more than one line.

Thanks Stephen, my apologies for not catching this during the merge.

> Stephen / Paul - do you want me to upload a new series for this or is
> this something you would normally do since it is a simple change?

I fixed it up and did a force push to selinux/next, it should be taken
care of now.

-- 
paul moore
www.paul-moore.com