From: Dan Williams <dan.j.williams@intel.com>
To: Dan Williams <dan.j.williams@intel.com>, <gregkh@linuxfoundation.org>
Cc: <rafael.j.wysocki@intel.com>, <tj@kernel.org>,
<linux-kernel@vger.kernel.org>, <regressions@lists.linux.dev>
Subject: Re: [PATCH v2] driver core: Fix userspace expectations of uevent_show() as a probe barrier
Date: Mon, 7 Oct 2024 17:26:57 -0700 [thread overview]
Message-ID: <67047c516045d_964fe294b1@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <172790598832.1168608.4519484276671503678.stgit@dwillia2-xfh.jf.intel.com>
Dan Williams wrote:
> Changes since v1 [1]:
> - Move the new "locked" infrastructure to private header files to make
> it clear it is not approved for general usage (Greg)
Greg, per the 0day report and further testing I am missing something
subtle in using kernfs open files to pin device objects. So hold off on
this for now until I can get that root caused. If someone else can spot
what I missed feel free to chime in, but otherwise I will circle back.
If I don't get back to this before -rc6 I think the theoretical deadlock
that would be re-introduced by a revert of 15fffc6a5624 would be
preferable to this reported regression. I am not aware of any reports of
that deadlock triggering in practice.
next prev parent reply other threads:[~2024-10-08 0:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 21:54 Dan Williams
2024-10-07 9:39 ` kernel test robot
2024-10-08 0:26 ` Dan Williams [this message]
2024-10-13 15:00 ` Greg KH
2024-10-28 9:08 ` Thorsten Leemhuis
2024-10-28 22:57 ` Dan Williams
2024-10-29 0:21 ` Greg KH
2024-12-31 7:56 ` Possible hungtask issue will be introduced with device_lock() in uevent_show() Zhang Zekun
2024-12-31 8:26 ` Greg KH
2025-01-04 6:02 ` zhangzekun (A)
2025-01-04 8:14 ` Greg KH
2025-01-23 2:07 ` Dan Williams
2025-01-27 3:27 ` zhangzekun (A)
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=67047c516045d_964fe294b1@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=regressions@lists.linux.dev \
--cc=tj@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
all inboxes | Powered by JetHome®