On Fri, Jun 5, 2020 at 3:54 PM Lakshmi Ramasubramanian <nramas@xxxxxxxxxxxxxxxxxxx> wrote: > On 6/5/20 12:37 PM, Paul Moore wrote: > > > If it's audit related, it's generally best to CC the linux-audit list, > > not just me (fixed). > > > > It's not clear to me what this pr_err() is trying to indicate other > > than *something* failed. Can someone provide some more background on > > this message? > > process_buffer_measurement() is currently used to measure > "kexec command line", "keys", and "blacklist-hash". If there was any > error in the measurement, this pr_err() will indicate which of the above > measurement failed and the related error code. > > Please let me know if you need more info on this one. That helps, thank you. > Since a pr_xyz() call was already present, I just wanted to change the > log level to keep the code change to the minimum. But if audit log is > the right approach for this case, I'll update. Generally we reserve audit for things that are required for various security certifications and/or "security relevant". From what you mentioned above, it seems like this would fall into the second category if not the first. Looking at your patch it doesn't look like you are trying to record anything special so you may be able to use the existing integrity_audit_msg(...) helper. Of course then the question comes down to the audit record type (the audit_msgno argument), the operation (op), and the comm/cause (cause). Do you feel that any of the existing audit record types are a good fit for this? -- paul moore www.paul-moore.com
