From: Jakob Koschel <jakobkoschel@gmail.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Peter Jones <pjones@redhat.com>,
linux-efi <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Brian Johannesmeyer <bjohannesmeyer@gmail.com>,
Cristiano Giuffrida <c.giuffrida@vu.nl>,
"Bos, H.J." <h.j.bos@vu.nl>
Subject: Re: [PATCH 1/2] efi: remove use of list iterator variable after loop
Date: Wed, 13 Apr 2022 20:08:09 +0200 [thread overview]
Message-ID: <9142505E-720F-401E-AD48-BA9D0880EDD1@gmail.com> (raw)
In-Reply-To: <CAMj1kXE2r4xrtFc+=OJfzutZzTtaUoFtW=f7y9+us9h+xGVEnA@mail.gmail.com>
> On 13. Apr 2022, at 19:05, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> On Fri, 1 Apr 2022 at 00:11, Jakob Koschel <jakobkoschel@gmail.com> wrote:
>>
>> In preparation to limiting the scope of a list iterator to the list
>> traversal loop, use a dedicated pointer to iterate through the list [1].
>>
>> In the current state the list_for_each_entry() is guaranteed to
>> hit a break or goto in order to work properly. If the list iterator
>> executes completely or the list is empty the iterator variable contains
>> a type confused bogus value infered from the head of the list.
>>
>> With this patch the variable used past the list iterator is only set
>> if the list exists early and is NULL otherwise. It should therefore
>> be safe to just set *prev = NULL (as it was before).
>>
>
> This generic boilerplate is fine to include, but it would help if you
> could point out why repainting the current logic with your new brush
> is appropriate here.
This makes sense, I can see that the commit message should be improved here.
>
> In this particular case, I wonder whether updating *prev makes sense
> to begin with if we are returning an error, and if we fix that, the
> issue disappears as well.
Actually I'm rethinking this now. The only use of 'prev' that I can see is
in efi_pstore_erase_name(). It only uses it if found != 0
which would mean err != 0 in __efivar_entry_iter().
This would allow massively simplifying the entire function.
The valid case is updating *prev when there is an "error" as far as I can tell.
I've sketched up a rewritten function that should hopefully be more clear and
archive the same goal, I'm curious what you think:
int __efivar_entry_iter(int (*func)(struct efivar_entry *, void *),
struct list_head *head, void *data,
struct efivar_entry **prev)
{
struct efivar_entry *entry, *n;
int err = 0;
/* If prev is set and *prev != NULL start iterating from there */
if (prev)
entry = list_prepare_entry(*prev, head, list);
/* Otherwise start at the beginning */
else
entry = list_entry(head, typeof(*entry), list);
list_for_each_entry_safe_continue(entry, n, head, list) {
err = func(entry, data);
if (err && prev)
*prev = entry;
if (err)
return err;
}
return 0;
}
next prev parent reply other threads:[~2022-04-13 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 22:10 Jakob Koschel
2022-03-31 22:10 ` [PATCH 2/2] efi: replace usage of found with dedicated list iterator variable Jakob Koschel
2022-04-13 17:09 ` Ard Biesheuvel
2022-04-13 17:05 ` [PATCH 1/2] efi: remove use of list iterator variable after loop Ard Biesheuvel
2022-04-13 18:08 ` Jakob Koschel [this message]
2022-04-13 22:09 ` Ard Biesheuvel
2022-06-28 8:02 ` Ard Biesheuvel
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=9142505E-720F-401E-AD48-BA9D0880EDD1@gmail.com \
--to=jakobkoschel@gmail.com \
--cc=ardb@kernel.org \
--cc=bjohannesmeyer@gmail.com \
--cc=c.giuffrida@vu.nl \
--cc=h.j.bos@vu.nl \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pjones@redhat.com \
--cc=rppt@kernel.org \
/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
all inboxes | Powered by JetHome®