grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Glenn Washburn <development@efficientek.com>
To: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	Daniel Kiper <dkiper@net-space.pl>
Subject: Re: [PATCH v2] efi: Fix stack protector issues
Date: Thu, 29 Feb 2024 15:29:47 -0600	[thread overview]
Message-ID: <20240229152947.2232d8b1@crass-HP-ZBook-15-G2> (raw)
In-Reply-To: <CAEaD8JNxBZXw+reQUCatLRbRdtY6GdGB4bKfd1AS=MJdXi4U0w@mail.gmail.com>

On Wed, 17 Jan 2024 06:10:29 +0300
"Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com> wrote:

> Looks good. A small comment inline
> 
> > diff --git a/grub-core/kern/main.c b/grub-core/kern/main.c
> > index 731c07c29..5db504e6e 100644
> > --- a/grub-core/kern/main.c
> > +++ b/grub-core/kern/main.c
> > @@ -265,6 +265,11 @@ reclaim_module_space (void)
> >  void __attribute__ ((noreturn))
> >  grub_main (void)
> >  {
> > +#ifdef GRUB_STACK_PROTECTOR
> > +  /* This call can only be made from a function that does not return. */
> Please add a bit of reasoning here not just in the commit message

I suspect Ard didn't see this as he wasn't CC'd. It would be good to
get this patch in (so I can rebase some old series and submit them to
the list). Daniel would you accept this as is? Or Ard can you update
the comment in this patch? My preference is for adding details to the
comment, but as my review suggests I'm fine with it as is.

Glenn

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

      reply	other threads:[~2024-02-29 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 17:42 [PATCH v2] efi: Fix stack protector issues Ard Biesheuvel via Grub-devel
2024-01-16  5:09 ` Glenn Washburn
2024-01-17  3:10 ` Vladimir 'phcoder' Serbinenko
2024-02-29 21:29   ` Glenn Washburn [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=20240229152947.2232d8b1@crass-HP-ZBook-15-G2 \
    --to=development@efficientek.com \
    --cc=ardb@kernel.org \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=phcoder@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).