linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wang Weiyang <wangweiyang2@huawei.com>
To: <zohar@linux.ibm.com>, <dmitry.kasatkin@gmail.com>,
	<jmorris@namei.org>, <serge@hallyn.com>
Cc: <linux-security-module@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-integrity@vger.kernel.org>,
	<wangweiyang2@huawei.com>
Subject: [PATCH 3/3] ima: Append line feed to ima/binary_runtime_measurements
Date: Thu, 5 May 2022 21:23:01 +0800	[thread overview]
Message-ID: <20220505132301.124832-4-wangweiyang2@huawei.com> (raw)
In-Reply-To: <20220505132301.124832-1-wangweiyang2@huawei.com>

There is no LF in binary_runtime_measurements output. It is little weird,
so append LF to it.

Example:

/ # cat /sys/kernel/security/ima/binary_runtime_measurements
...imaboot_aggregate/ #

Signed-off-by: Wang Weiyang <wangweiyang2@huawei.com>
---
 security/integrity/ima/ima_fs.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/security/integrity/ima/ima_fs.c b/security/integrity/ima/ima_fs.c
index cd1683dad3bf..0a2f9cb25b20 100644
--- a/security/integrity/ima/ima_fs.c
+++ b/security/integrity/ima/ima_fs.c
@@ -183,6 +183,7 @@ int ima_measurements_show(struct seq_file *m, void *v)
 			show = IMA_SHOW_BINARY_OLD_STRING_FMT;
 		field->field_show(m, show, &e->template_data[i]);
 	}
+	seq_puts(m, "\n");
 	return 0;
 }
 
-- 
2.17.1


  parent reply	other threads:[~2022-05-05 13:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 13:22 [PATCH 0/3] Append line feed to files in securityfs Wang Weiyang
2022-05-05 13:22 ` [PATCH 1/3] securityfs: Append line feed to /sys/kernel/security/lsm Wang Weiyang
2022-05-05 16:29   ` Casey Schaufler
2022-05-05 13:23 ` [PATCH 2/3] evm: Append line feed to /sys/kernel/security/evm Wang Weiyang
2022-05-05 13:23 ` Wang Weiyang [this message]
2022-05-06 11:16   ` [PATCH 3/3] ima: Append line feed to ima/binary_runtime_measurements Mimi Zohar
2022-05-06 12:31     ` wangweiyang

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=20220505132301.124832-4-wangweiyang2@huawei.com \
    --to=wangweiyang2@huawei.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=serge@hallyn.com \
    --cc=zohar@linux.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;
as well as URLs for NNTP newsgroup(s).