From: Greg KH <gregkh@linuxfoundation.org>
To: John Johansen <john.johansen@canonical.com>
Cc: Loic <hackurx@opensec.fr>,
stable@vger.kernel.org, arnd@arndb.de, james.l.morris@oracle.com
Subject: Re: [PATCH] apparmor: fix SECURITY_APPARMOR_HASH_DEFAULT parameter handling
Date: Mon, 17 Sep 2018 15:58:27 +0200 [thread overview]
Message-ID: <20180917135827.GA28797@kroah.com> (raw)
In-Reply-To: <8d87110d-eeab-17ad-b131-a12e321bff4b@canonical.com>
On Mon, Sep 17, 2018 at 06:40:20AM -0700, John Johansen wrote:
> On 09/17/2018 04:49 AM, Greg KH wrote:
> > On Sun, Sep 09, 2018 at 04:04:18PM +0200, Loic wrote:
> >> Hello,
> >>
> >> Tested without any problem so please picked up this for 4.4 to fix the
> >> problem.
> >> The patch below is slightly modified to adapt to this version.
> >
> > I would like to get an ack from one of the developers/maintainers of
> > this patch before I accept it, as it does differ from the in-tree
> > version a bit.
> >
>
> Greg the patch is good. Full explanation below
>
>
> cherry-picking the original patch to 4.4, I get 2 conflicts
>
> both modified: security/apparmor/lsm.c
> both modified: security/apparmor/policy_unpack.c
>
> the lsm.c conflict is do to surrounding code changes and is handled
> correctly. The patch drops the policy_unpack.c change
Great, thanks for reviewing this!
greg k-h
next prev parent reply other threads:[~2018-09-17 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 14:04 [PATCH] apparmor: fix SECURITY_APPARMOR_HASH_DEFAULT parameter handling Loic
2018-09-17 11:49 ` Greg KH
2018-09-17 13:40 ` John Johansen
2018-09-17 13:58 ` Greg KH [this message]
2018-09-17 13:58 ` Greg KH
2018-09-17 19:45 ` Loic
2018-09-17 21:15 ` Greg KH
2018-09-17 21:37 ` Greg KH
2018-09-17 21:56 ` Nathan Chancellor
2018-09-17 22:12 ` John Johansen
2018-09-21 5:40 ` Loic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180917135827.GA28797@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=hackurx@opensec.fr \
--cc=james.l.morris@oracle.com \
--cc=john.johansen@canonical.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox