linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	 kernel-team@meta.com,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	 Borislav Petkov <bp@suse.de>, Andy Lutomirski <luto@kernel.org>,
	Kees Cook <kees@kernel.org>,  Tony Luck <tony.luck@intel.com>,
	"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
	 Thomas Gleixner <tglx@kernel.org>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v3 0/7] efi/runtime-wrappers: bound the wait for EFI runtime service calls
Date: Fri, 10 Jul 2026 03:06:43 -0700	[thread overview]
Message-ID: <alDDv3XGXVdd1mri@gmail.com> (raw)
In-Reply-To: <361838e6-76e6-4ad3-95ab-994a56bf5f9e@app.fastmail.com>

On Thu, Jul 09, 2026 at 08:02:28AM +0300, Ard Biesheuvel wrote:
> 
> 
> On Wed, 1 Jul 2026, at 15:28, Breno Leitao wrote:
> > Hello Ard,
> >
> > On Tue, Jun 16, 2026 at 05:09:33AM -0700, Breno Leitao wrote:
> >> When an EFI runtime service call hangs in firmware, the kworker on
> >> efi_rts_wq is stuck inside the firmware call and cannot be cancelled.
> >> The kernel currently waits indefinitely on the completion, and the
> >> caller holds efi_runtime_lock for the duration, so every subsequent
> >> EFI runtime caller (efivarfs, NVRAM writes, set_wakeup_time, ACPI PRM
> >> handlers, ...) is wedged until reboot. The only externally visible
> >> symptom is a "workqueue lockup" message and userspace processes
> >> piling up uninterruptibly on the semaphore.
> >
> > I'd appreciate your thoughts on this approach. Is there anything you'd
> > like me to adjust or improve before we move forward?
> >
> 
> This looks fine now, apologies for the delayed response.
> 
> I've queued this up for v7.3

Thanks, Ard.

We got two reports that I would like to address:

1) efi_rts_park_worker() should be tagged as __noreturn
https://lore.kernel.org/all/202607100848.iWPxdkhX-lkp@intel.com/

2) efi_runtime_lock_owner() is undeclared in some kernel config
https://lore.kernel.org/all/202607100518.uMJJPDfP-lkp@intel.com/

Do you want me to respin this series, or, some fixes on top of current
tree?

Thanks,
--breno

      reply	other threads:[~2026-07-10 10:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 12:09 [PATCH v3 0/7] efi/runtime-wrappers: bound the wait for EFI runtime service calls Breno Leitao
2026-06-16 12:09 ` [PATCH v3 1/7] efi: fix stale reference to efi_recover_from_page_fault() Breno Leitao
2026-06-16 12:09 ` [PATCH v3 2/7] efi/runtime-wrappers: factor out efi_rts_park_worker() Breno Leitao
2026-06-16 12:09 ` [PATCH v3 3/7] efi/runtime-wrappers: handle queue_work() failure with goto exit Breno Leitao
2026-06-16 12:09 ` [PATCH v3 4/7] efi/runtime-wrappers: check EFI_RUNTIME_SERVICES before using efi_rts_work Breno Leitao
2026-06-16 12:09 ` [PATCH v3 5/7] efi/runtime-wrappers: bound the wait for EFI runtime service calls Breno Leitao
2026-07-09  6:56   ` Yeoreum Yun
2026-07-10 10:30     ` Breno Leitao
2026-07-10 10:41       ` Yeoreum Yun
2026-07-10 11:14         ` Breno Leitao
2026-07-10 11:26           ` Yeoreum Yun
2026-07-10 13:47             ` Breno Leitao
2026-06-16 12:09 ` [PATCH v3 6/7] efi/runtime-wrappers: honour EFI_RUNTIME_SERVICES in the non-blocking paths Breno Leitao
2026-06-16 12:09 ` [PATCH v3 7/7] efi/runtime-wrappers: retire the worker if a wedged call ever returns Breno Leitao
2026-07-01 12:28 ` [PATCH v3 0/7] efi/runtime-wrappers: bound the wait for EFI runtime service calls Breno Leitao
2026-07-09  5:02   ` Ard Biesheuvel
2026-07-10 10:06     ` Breno Leitao [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=alDDv3XGXVdd1mri@gmail.com \
    --to=leitao@debian.org \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gpiccoli@igalia.com \
    --cc=hpa@zytor.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kees@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).