All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ted Brandston <tbrandston@google.com>
Cc: ardb@kernel.org, linux-efi@vger.kernel.org,
	stable@vger.kernel.org, Jiao Zhou <jiaozhou@google.com>,
	Nicholas Bishop <nicholasbishop@google.com>
Subject: Re: efivarfs fixes without the commit being fixed in 6.1 and 6.6 (resending without html)
Date: Thu, 21 Mar 2024 15:58:56 +0100	[thread overview]
Message-ID: <2024032132-fax-unsmooth-f92b@gregkh> (raw)
In-Reply-To: <CA+eDQTEiRyddZYwmyX3q+1bBgFRQydC++i4DDbiQ+zC-j72FVQ@mail.gmail.com>

On Thu, Mar 21, 2024 at 10:43:05AM -0400, Ted Brandston wrote:
> Hi, this is my first time posting to a kernel list (third try, finally
> figured out the html-free -- sorry for the noise).
> 
> I noticed that in the 6.6 kernel there's a fix commit from Ard [1] but
> not the commit it's fixing ("efivarfs: Add uid/gid mount options").
> Same thing in 6.1 [2]. The commit being fixed doesn't appear until 6.7
> [3].
> 
> I'm not familiar with this code so it's unclear to me if this might
> cause problems, but I figured I should point it out.
> 
> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/efivarfs/super.c?h=linux-6.6.y&id=48be1364dd387e375e1274b76af986cb8747be2c
> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/fs/efivarfs/super.c?h=linux-6.1.y
> [3]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/fs/efivarfs/super.c?h=linux-6.7.y

Good catch.  Ard, should this be reverted?

thanks,

greg k-h

  reply	other threads:[~2024-03-21 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+eDQTFQ45nWGmctp-CkK=xXXQQHc_DTkM1iN4m-0o5fCjt8VA@mail.gmail.com>
2024-03-21 14:43 ` efivarfs fixes without the commit being fixed in 6.1 and 6.6 (resending without html) Ted Brandston
2024-03-21 14:58   ` Greg KH [this message]
2024-03-21 15:28     ` Ard Biesheuvel
2024-03-21 15:34       ` Greg KH

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=2024032132-fax-unsmooth-f92b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ardb@kernel.org \
    --cc=jiaozhou@google.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=nicholasbishop@google.com \
    --cc=stable@vger.kernel.org \
    --cc=tbrandston@google.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 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.