From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com> To: Mimi Zohar <zohar@linux.ibm.com>, sgrubb@redhat.com, paul@paul-moore.com Cc: rgb@redhat.com, linux-integrity@vger.kernel.org, linux-audit@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 2/2] IMA: Add audit log for failure conditions Date: Wed, 24 Jun 2020 10:25:16 -0700 [thread overview] Message-ID: <39d66bdc-55be-984a-42a0-34d0a011e0fb@linux.microsoft.com> (raw) In-Reply-To: <1592942295.5389.9.camel@linux.ibm.com> On 6/23/20 12:58 PM, Mimi Zohar wrote: Hi Steve\Paul, >> Sample audit messages: >> >> [ 6.303048] audit: type=1804 audit(1592506281.627:2): pid=1 uid=0 >> auid=4294967295 ses=4294967295 subj=kernel op=measuring_key >> cause=ENOMEM comm="swapper/0" name=".builtin_trusted_keys" res=0 >> errno=-12 > > My only concern is that auditing -ENOMEM will put additional memory > pressure on the system. I'm not sure if this is a concern and, if so, > how it should be handled. Do you have any concerns with respect to adding audit messages in low memory conditions? > > Reviewed-by: Mimi Zohar <zohar@linux.ibm.com> Thanks Mimi -lakshmi
WARNING: multiple messages have this Message-ID (diff)
From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com> To: Mimi Zohar <zohar@linux.ibm.com>, sgrubb@redhat.com, paul@paul-moore.com Cc: rgb@redhat.com, linux-integrity@vger.kernel.org, linux-audit@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 2/2] IMA: Add audit log for failure conditions Date: Wed, 24 Jun 2020 10:25:16 -0700 [thread overview] Message-ID: <39d66bdc-55be-984a-42a0-34d0a011e0fb@linux.microsoft.com> (raw) In-Reply-To: <1592942295.5389.9.camel@linux.ibm.com> On 6/23/20 12:58 PM, Mimi Zohar wrote: Hi Steve\Paul, >> Sample audit messages: >> >> [ 6.303048] audit: type=1804 audit(1592506281.627:2): pid=1 uid=0 >> auid=4294967295 ses=4294967295 subj=kernel op=measuring_key >> cause=ENOMEM comm="swapper/0" name=".builtin_trusted_keys" res=0 >> errno=-12 > > My only concern is that auditing -ENOMEM will put additional memory > pressure on the system. I'm not sure if this is a concern and, if so, > how it should be handled. Do you have any concerns with respect to adding audit messages in low memory conditions? > > Reviewed-by: Mimi Zohar <zohar@linux.ibm.com> Thanks Mimi -lakshmi -- Linux-audit mailing list Linux-audit@redhat.com https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2020-06-24 17:25 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-18 21:10 [PATCH v3 1/2] integrity: Add errno field in audit message Lakshmi Ramasubramanian 2020-06-18 21:10 ` Lakshmi Ramasubramanian 2020-06-18 21:10 ` [PATCH v3 2/2] IMA: Add audit log for failure conditions Lakshmi Ramasubramanian 2020-06-18 21:10 ` Lakshmi Ramasubramanian 2020-06-23 19:58 ` Mimi Zohar 2020-06-23 19:58 ` Mimi Zohar 2020-06-24 17:25 ` Lakshmi Ramasubramanian [this message] 2020-06-24 17:25 ` Lakshmi Ramasubramanian 2020-06-25 19:14 ` Paul Moore 2020-06-25 19:14 ` Paul Moore 2020-06-29 16:57 ` Mimi Zohar 2020-06-29 16:57 ` Mimi Zohar 2020-06-22 22:27 ` [PATCH v3 1/2] integrity: Add errno field in audit message Mimi Zohar 2020-06-22 22:27 ` Mimi Zohar 2020-06-24 0:07 ` Paul Moore 2020-06-24 0:07 ` Paul Moore
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=39d66bdc-55be-984a-42a0-34d0a011e0fb@linux.microsoft.com \ --to=nramas@linux.microsoft.com \ --cc=linux-audit@redhat.com \ --cc=linux-integrity@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=paul@paul-moore.com \ --cc=rgb@redhat.com \ --cc=sgrubb@redhat.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.