From: Casey Schaufler <casey@schaufler-ca.com>
To: Maninder Singh <maninder1.s@samsung.com>,
jmorris@namei.org, serge@hallyn.com
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, a.sahrawat@samsung.com,
v.narang@samsung.com, Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH 1/1] smack: remove redundant structure variable from header.
Date: Thu, 9 Apr 2020 14:00:13 -0700 [thread overview]
Message-ID: <91af6ae1-919a-bc48-1f62-6ba3b4c62dac@schaufler-ca.com> (raw)
In-Reply-To: <1586435998-18921-1-git-send-email-maninder1.s@samsung.com>
On 4/9/2020 5:39 AM, Maninder Singh wrote:
> commit afb1cbe37440 ("LSM: Infrastructure management
> of the inode security") removed usage of smk_rcu,
> thus removing it from structure.
>
> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
> Signed-off-by: Vaneet Narang <v.narang@samsung.com>
Thank you. I will take this.
> ---
> security/smack/smack.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/security/smack/smack.h b/security/smack/smack.h
> index 62529f3..5ebd0bb 100644
> --- a/security/smack/smack.h
> +++ b/security/smack/smack.h
> @@ -111,7 +111,6 @@ struct inode_smack {
> struct smack_known *smk_mmap; /* label of the mmap domain */
> struct mutex smk_lock; /* initialization lock */
> int smk_flags; /* smack inode flags */
> - struct rcu_head smk_rcu; /* for freeing inode_smack */
> };
>
> struct task_smack {
prev parent reply other threads:[~2020-04-09 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200409124013epcas5p33036c008f30327378a6ff02050261626@epcas5p3.samsung.com>
2020-04-09 12:39 ` [PATCH 1/1] smack: remove redundant structure variable from header Maninder Singh
2020-04-09 21:00 ` 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=91af6ae1-919a-bc48-1f62-6ba3b4c62dac@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=a.sahrawat@samsung.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=serge@hallyn.com \
--cc=v.narang@samsung.com \
/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;
as well as URLs for NNTP newsgroup(s).