LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com> To: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com> Cc: linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, James Morris <jmorris@namei.org>, "Serge E. Hallyn" <serge@hallyn.com>, Mimi Zohar <zohar@linux.vnet.ibm.com>, Dmitry Kasatkin <dmitry.kasatkin@gmail.com> Subject: Re: [PATCH 2/4] ima: Simplify ima_eventsig_init() Date: Wed, 14 Mar 2018 16:31:34 -0500 [thread overview] Message-ID: <20180314213134.GA14289@mail.hallyn.com> (raw) In-Reply-To: <20180314202020.3794-3-bauerman@linux.vnet.ibm.com> Quoting Thiago Jung Bauermann (bauerman@linux.vnet.ibm.com): > The "goto out" statement doesn't have any purpose since there's no cleanup > to be done when returning early, so remove it. This also makes the rc > variable unnecessary so remove it as well. > > Also, the xattr_len and fmt variables are redundant so remove them as well. > > Signed-off-by: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com> Acked-by: Serge Hallyn <serge@hallyn.com> > --- > security/integrity/ima/ima_template_lib.c | 11 +++-------- > 1 file changed, 3 insertions(+), 8 deletions(-) > > diff --git a/security/integrity/ima/ima_template_lib.c b/security/integrity/ima/ima_template_lib.c > index 28af43f63572..5afaa53decc5 100644 > --- a/security/integrity/ima/ima_template_lib.c > +++ b/security/integrity/ima/ima_template_lib.c > @@ -378,16 +378,11 @@ int ima_eventname_ng_init(struct ima_event_data *event_data, > int ima_eventsig_init(struct ima_event_data *event_data, > struct ima_field_data *field_data) > { > - enum data_formats fmt = DATA_FMT_HEX; > struct evm_ima_xattr_data *xattr_value = event_data->xattr_value; > - int xattr_len = event_data->xattr_len; > - int rc = 0; > > if ((!xattr_value) || (xattr_value->type != EVM_IMA_XATTR_DIGSIG)) > - goto out; > + return 0; > > - rc = ima_write_template_field_data(xattr_value, xattr_len, fmt, > - field_data); > -out: > - return rc; > + return ima_write_template_field_data(xattr_value, event_data->xattr_len, > + DATA_FMT_HEX, field_data); > }
next prev parent reply other threads:[~2018-03-14 21:31 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-14 20:20 [PATCH 0/4] Code improvements in integrity and IMA Thiago Jung Bauermann 2018-03-14 20:20 ` [PATCH 1/4] integrity: Remove unused macro IMA_ACTION_RULE_FLAGS Thiago Jung Bauermann 2018-03-14 21:33 ` Serge E. Hallyn 2018-03-14 20:20 ` [PATCH 2/4] ima: Simplify ima_eventsig_init() Thiago Jung Bauermann 2018-03-14 21:31 ` Serge E. Hallyn [this message] 2018-03-14 20:20 ` [PATCH 3/4] ima: Improvements in ima_appraise_measurement() Thiago Jung Bauermann 2018-03-14 21:40 ` Serge E. Hallyn 2018-03-15 0:03 ` Thiago Jung Bauermann 2018-03-15 19:18 ` Mimi Zohar 2018-03-15 20:33 ` Thiago Jung Bauermann 2018-03-17 15:09 ` Serge E. Hallyn 2018-03-14 20:20 ` [PATCH 4/4] integrity: Introduce struct evm_xattr Thiago Jung Bauermann 2018-03-15 21:01 ` [PATCH 0/4] Code improvements in integrity and IMA Mimi Zohar
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=20180314213134.GA14289@mail.hallyn.com \ --to=serge@hallyn.com \ --cc=bauerman@linux.vnet.ibm.com \ --cc=dmitry.kasatkin@gmail.com \ --cc=jmorris@namei.org \ --cc=linux-integrity@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=zohar@linux.vnet.ibm.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: linkBe 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).