From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Richard Hughes <richard@hughsie.com>, linux-efi@vger.kernel.org
Subject: Re: efivarfs: fix error on write to new variable leaving remnants
Date: Wed, 26 Feb 2025 08:02:43 -0500 [thread overview]
Message-ID: <0ebb2fc8cbab6be663ad7504db3b7d89d0f2ae5c.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAMj1kXGsZVAWmG7NV+6fevvZy6RwEXrw2avT1EBRWjn5Kk_hvw@mail.gmail.com>
On Wed, 2025-02-26 at 12:30 +0100, Ard Biesheuvel wrote:
> On Tue, 25 Feb 2025 at 13:59, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> > [added correct mailing list for bug report]
> > On Tue, 2025-02-25 at 12:10 +0000, Richard Hughes wrote:
> > > Hi,
> > >
> > > I'm not sure what I'm supposed to do about:
> > >
> > > commit 908af31f4896f2c0645031f8b74a89d3a8beb5b9
> > > Author: James Bottomley <James.Bottomley@HansenPartnership.com>
> > > Date: Sun Jan 19 10:12:12 2025 -0500
> > >
> > > efivarfs: fix error on write to new variable leaving remnants
> > >
> ...
> > >
> > > It causes a regression in fwupd -- seen in
> > > https://github.com/fwupd/fwupd/issues/8495 and
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2346831 so far -- and
> > > it seems broken for anyone (including me) updating to 6.14.
> >
> > OK, so the problem with this as a bug report is that it doesn't
> > explain what you're doing. However
> >
> > > I can work around the behavior in
> > > https://github.com/fwupd/fwupd/pull/8500 (which is also the
> > > arguably correct thing to do) but it's going to cause a panic as
> > > I have to get an updated fwupd out on all distros so we'll need
> > > releases for multiple branches.
>
> This code was introduced in the merge window for v6.14, which is due
> to be released end of March. How much time do you need?
The request in the original was for a few more months.
> Derailing LVFS is the last thing I want to do, but we all know how
> this works: once a workaround is put in, it is never going to be
> removed.
I think simply queueing the workaround now (If it works; I'd still like
to see a tested by since it's nowhere near a pure revert) in the fixes
branch for the v14-rc and immediately queueing its revert in the
updates for v15 would give an additional three months automatically and
no-one would have to do anything more (unless more time were needed).
Regards,
James
next prev parent reply other threads:[~2025-02-26 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SBFUY-p4-fI9JOrQa51x141vKHs_rbFLw4q9kfPGAK8Z76PQfgYl6zM3nUjlOeIPY6PgEhqLFaSJkW0vdBVzET3MDYUBZwzmYCJuNK4TaYU=@hughsie.com>
2025-02-25 12:59 ` efivarfs: fix error on write to new variable leaving remnants James Bottomley
2025-02-26 11:30 ` Ard Biesheuvel
2025-02-26 13:02 ` James Bottomley [this message]
2025-02-26 13:09 ` James Bottomley
2025-02-26 14:27 ` Richard Hughes
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=0ebb2fc8cbab6be663ad7504db3b7d89d0f2ae5c.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=richard@hughsie.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