From: Petr Vorel <pvorel@suse.cz>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: ltp@lists.linux.it, Stefan Berger <stefanb@linux.ibm.com>,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH v2 1/4] ima_violations.sh: force $LOG ToMToU violation earlier
Date: Tue, 4 Mar 2025 14:34:50 +0100 [thread overview]
Message-ID: <20250304133450.GD81126@pevik> (raw)
In-Reply-To: <30769565910b3198fa8d714b5edb25419fcb1457.camel@linux.ibm.com>
Hi Mimi,
...
> > > + exec 3< $LOG || tst_brk TBROK "failed to read log file"
> > > tst_res TINFO "using log $LOG"
> > If you don't mind, I would reverse the order to get info about which log is
> > used:
> > tst_res TINFO "using log $LOG"
> > exec 3< $LOG || tst_brk TBROK "failed to read log file"
> Oh, I see what you mean. All of the TINFO come first and then an error, if
> there is one. That's fine.
Good. Merged this patch.
Kind regards,
Petr
prev parent reply other threads:[~2025-03-04 13:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 11:53 [PATCH v2 1/4] ima_violations.sh: force $LOG ToMToU violation earlier Mimi Zohar
2025-03-04 11:53 ` [PATCH v2 2/4] ima_violations.sh: Update validate() to support multiple violations Mimi Zohar
2025-03-04 13:31 ` Petr Vorel
2025-03-04 14:44 ` Mimi Zohar
2025-03-04 14:59 ` Mimi Zohar
2025-03-04 17:43 ` Petr Vorel
2025-03-04 21:33 ` Mimi Zohar
2025-03-04 11:53 ` [PATCH v2 3/4] ima_violations.sh: additional open-writer violation tests Mimi Zohar
2025-03-04 11:53 ` [PATCH v2 4/4] ima_violations.sh: additional ToMToU " Mimi Zohar
2025-03-04 12:57 ` [PATCH v2 1/4] ima_violations.sh: force $LOG ToMToU violation earlier Petr Vorel
2025-03-04 13:06 ` Mimi Zohar
2025-03-04 13:34 ` Petr Vorel [this message]
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=20250304133450.GD81126@pevik \
--to=pvorel@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=stefanb@linux.ibm.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