All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Williams <dan.j.williams@intel.com>
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: Sun, 13 Oct 2024 17:00:15 +0200	[thread overview]
Message-ID: <2024101356-gauntlet-sludge-7b76@gregkh> (raw)
In-Reply-To: <67047c516045d_964fe294b1@dwillia2-xfh.jf.intel.com.notmuch>

On Mon, Oct 07, 2024 at 05:26:57PM -0700, Dan Williams wrote:
> 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.

Ok, I'll drop this for now and wait for a follow-on patch to come for
whatever you decide.

thanks,

greg k-h

  reply	other threads:[~2024-10-13 15:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 21:54 [PATCH v2] driver core: Fix userspace expectations of uevent_show() as a probe barrier Dan Williams
2024-10-07  9:39 ` kernel test robot
2024-10-08  0:26 ` Dan Williams
2024-10-13 15:00   ` Greg KH [this message]
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=2024101356-gauntlet-sludge-7b76@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.j.williams@intel.com \
    --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 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.