All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: 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: Wed, 1 Jul 2026 05:28:42 -0700	[thread overview]
Message-ID: <akUG8giyFn2a3Lts@gmail.com> (raw)
In-Reply-To: <20260616-efi_timeout-v3-0-76dd1d26657b@debian.org>

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?

Thanks,
--breno

  parent reply	other threads:[~2026-07-01 12:28 UTC|newest]

Thread overview: 19+ 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-07-12 16:25               ` Ard Biesheuvel
2026-07-13 10:03                 ` 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 ` Breno Leitao [this message]
2026-07-09  5:02   ` [PATCH v3 0/7] efi/runtime-wrappers: bound the wait for EFI runtime service calls Ard Biesheuvel
2026-07-10 10:06     ` Breno Leitao

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=akUG8giyFn2a3Lts@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 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.