mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Linux regressions mailing list" <regressions@lists.linux.dev>
Cc: Dan Williams <dan.j.williams@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [regression] frozen usb mouse pointer at boot
Date: Sun, 22 Sep 2024 04:47:25 +0200	[thread overview]
Message-ID: <66ef853de5f16_10a0a2946e@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
In-Reply-To: <2024091128-imperial-purchase-f5e7@gregkh>

Greg Kroah-Hartman wrote:
[..]
> 
> This is odd.
> 
> Does the latest 6.10.y release also show this problem?
> 
> I can't duplicate this here, and it's the first I've heard of it (given
> that USB mice are pretty popular, I would suspect others would have hit
> it as well...)

Sorry for missing this earlier. One thought is that userspace has a
dependency on uevent_show() flushing device probing. In other words the
side effect of taking the device_lock() in uevent_show() is that udev
might enjoy some occasions where the reading the uevent flushes probing
before the udev rule runs. With this change, uevent_show() no longer
waits for any inflight probes to complete.

One idea to fix this problem is to create a special case sysfs attribute
type that takes the device_lock() before kernfs_get_active() to avoid
the deadlock on attribute teardown.

I'll take a look. Thanks for forwarding the report Thorsten!

  reply	other threads:[~2024-09-22  2:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  7:55 Linux regression tracking (Thorsten Leemhuis)
2024-09-11  9:43 ` Greg Kroah-Hartman
2024-09-22  2:47   ` Dan Williams [this message]
2024-09-24  2:54     ` Dan Williams
2024-09-27  8:59       ` Linux regression tracking (Thorsten Leemhuis)
2024-09-27 20:52         ` Dan Williams

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=66ef853de5f16_10a0a2946e@dwillia2-mobl3.amr.corp.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.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®