From: James Morris <jmorris@namei.org>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
LSM <linux-security-module@vger.kernel.org>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [PULL] Smack: Mark inode instant in smack_task_to_inode
Date: Tue, 26 Jun 2018 03:05:23 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1806260304580.26153@namei.org> (raw)
In-Reply-To: <813ecc0b-4a9e-22c9-b893-504936bab342@schaufler-ca.com>
On Mon, 25 Jun 2018, Casey Schaufler wrote:
> James, would you please pull this change for 4.18.
I already have it queued for Linus, I'll send it up probably today.
>
> Al Viro's /proc clean-up in commit 1bbc55131e59bd099fdc568d3aa0b42634dbd188
> created a regression in Smack xattr behavior in /proc. This fixes that problem
> with a minimum of fuss.
>
>
> The following changes since commit 0f8983cf97d3327531b7843c831517cac3a1b9ed:
>
> Smack: Fix memory leak in smack_inode_getsecctx (2018-06-05 12:16:01 -0700)
>
> are available in the Git repository at:
>
> git://github.com/cschaufler/next-smack smack-for-4.18
>
> for you to fetch changes up to aabfe8e2d9f49153bafefc82d10bcb6e1e12828d:
>
> Smack: Mark inode instant in smack_task_to_inode (2018-06-22 13:55:28 -0700)
>
> ----------------------------------------------------------------
> Casey Schaufler (1):
> Smack: Mark inode instant in smack_task_to_inode
>
> security/smack/smack_lsm.c | 1 +
> 1 file changed, 1 insertion(+)
>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2018-06-25 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 16:41 Casey Schaufler
2018-06-25 17:05 ` James Morris [this message]
2018-06-25 17:16 ` Casey Schaufler
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=alpine.LRH.2.21.1806260304580.26153@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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
all inboxes | Powered by JetHome®