From: Joe Perches <joe@perches.com>
To: "Bruno E. O. Meneguele" <brdeoliv@redhat.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Cc: linux-integrity@vger.kernel.org,
linux-ima-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ima: log message to module appraisal error
Date: Mon, 04 Dec 2017 15:35:37 -0800 [thread overview]
Message-ID: <1512430537.6321.58.camel@perches.com> (raw)
In-Reply-To: <20171204202347.16261-1-brdeoliv@redhat.com>
On Mon, 2017-12-04 at 18:23 -0200, Bruno E. O. Meneguele wrote:
> Simple but useful message log to the user in case of module appraise is
> forced and fails due to the lack of file descriptor, that might be
> caused by kmod calls to compressed modules.
[]
> diff --git a/security/integrity/ima/ima_main.c b/security/integrity/ima/ima_main.c
[]
> @@ -366,8 +366,12 @@ int ima_read_file(struct file *file, enum kernel_read_file_id read_id)
>
> if (!file && read_id == READING_MODULE) {
> if (!sig_enforce && (ima_appraise & IMA_APPRAISE_MODULES) &&
> - (ima_appraise & IMA_APPRAISE_ENFORCE))
> + (ima_appraise & IMA_APPRAISE_ENFORCE)) {
> + pr_err("impossible to appraise a module without a file \
> + descriptor. sig_enforce kernel parameter might \
> + help\n");
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You should probably use scripts/checkpatch.pl on your proposed
patches
before sending them.
You've got a lot of tabs and spaces after every line continuation.
Please coalesce the format on a single line and avoid this defect.
pr_err("impossible to appraise a module without a file descriptor. sig_enforce kernel parameter might help\n");
cheers, Joe
next prev parent reply other threads:[~2017-12-04 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 20:23 [PATCH v2] ima: log message to module appraisal error Bruno E. O. Meneguele
2017-12-04 23:35 ` Joe Perches [this message]
2017-12-05 10:05 ` Bruno E. O. Meneguele
-- strict thread matches above, loose matches on Subject: below --
2017-12-05 13:35 Bruno E. O. Meneguele
2017-12-05 13:40 ` Bruno E. O. Meneguele
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=1512430537.6321.58.camel@perches.com \
--to=joe@perches.com \
--cc=brdeoliv@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-ima-devel@lists.sourceforge.net \
--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: 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