Linux Security Modules development
 help / color / mirror / Atom feed
From: casey@schaufler-ca.com (Casey Schaufler)
To: linux-security-module@vger.kernel.org
Subject: [PULL] Smack: Changes for 4.15
Date: Wed, 1 Nov 2017 17:35:33 -0700	[thread overview]
Message-ID: <d74eb33a-0c72-c947-09bd-61246cce4d46@schaufler-ca.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1711021117140.16891@localhost>

Hmm. I pulled from your next-general branch.
I had already pulled from your "next" branch when all the bruhaha
hit, so that may be what you see in the tree. This may be an artifact
of the "process" change.


On 11/1/2017 5:18 PM, James Morris wrote:
> On Wed, 1 Nov 2017, Casey Schaufler wrote:
>
>> Only one change for Smack for 4.15. A fix for overlayfs handling.
>>
>> The following changes since commit eb95b40b45a1ee4218cab0e6c72dd014d8f09bee:
>>
>>   Merge branch 'next-general' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security into next (2017-09-25 11:03:43 -0700)
>>
>> are available in the git repository at:
>>
>>   git://github.com/cschaufler/smack-next smack-for-4.15
>>
>> for you to fetch changes up to c31a5d0182e7b76392295b9a9a5637ca1022c450:
>>
>>   Smack: Base support for overlayfs (2017-10-16 12:13:12 -0700)
>>
>> ----------------------------------------------------------------
>> Casey Schaufler (1):
>>       Smack: Base support for overlayfs
>>
>>  security/smack/smack_lsm.c | 79 ++++++++++++++++++++++++++++++++++++++++++++++
>>  1 file changed, 79 insertions(+)
> I'll cherry pick this but it looks like you're pulling stuff into your 
> tree from Linus (including the IMA & Tomoyo changes which Paul 
> acccidentally sent).
>
> Please base your tree off next-general, not Linus.
>
>
> - James

--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2017-11-02  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 23:56 [PULL] Smack: Changes for 4.15 Casey Schaufler
2017-11-02  0:18 ` James Morris
2017-11-02  0:35   ` Casey Schaufler [this message]

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=d74eb33a-0c72-c947-09bd-61246cce4d46@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=linux-security-module@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