From: John Garry <john.g.garry@oracle.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: russ.weight@linux.dev, gregkh@linuxfoundation.org,
rafael@kernel.org, linux-kernel@vger.kernel.org,
masahiroy@kernel.org
Subject: Re: [PATCH] firmware_loader: Use init_utsname()->release
Date: Wed, 28 Feb 2024 12:31:42 +0000 [thread overview]
Message-ID: <a07db8f8-39f8-44ad-b466-10ac02f3da13@oracle.com> (raw)
In-Reply-To: <Zd3oke0pAL2G05Rj@bombadil.infradead.org>
On 27/02/2024 13:50, Luis Chamberlain wrote:
> On Tue, Feb 27, 2024 at 01:02:26PM +0000, John Garry wrote:
>> On 27/02/2024 12:59, Luis Chamberlain wrote:
>>> What kernel are you seeing this issue on?
>> I was testing v6.8-rc5 last week
> I cannot reproduce a hung task there either on that kernel.
>
> I see this:
>
> sysfs: cannot create duplicate filename '/devices/virtual/misc/test_firmware/nope-test-firmware.bin'
>
> But these are expected as the selftests tries silly things to ensure
> they are not allowed.
>
> If you can reproduce it there, it would be appreciated if you look underneath
> the hood a bit, or share anything glaring and obvious which may help
> reproduce this.
Update: commenting-out /lib/udev/rules.d/50-firmware.rules seems to make
the test reliably pass for v6.8-rc5, but not with my patch on top - I
still get a hang there. I'll investigate that hang with my patch.
Thanks,
John
next prev parent reply other threads:[~2024-02-28 12:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 14:58 John Garry
2024-02-22 15:53 ` Luis Chamberlain
2024-02-23 14:29 ` John Garry
2024-02-23 15:34 ` John Garry
2024-02-26 16:34 ` Luis Chamberlain
2024-02-26 17:10 ` Luis Chamberlain
2024-02-26 17:13 ` John Garry
2024-02-27 12:59 ` Luis Chamberlain
2024-02-27 13:02 ` John Garry
2024-02-27 13:50 ` Luis Chamberlain
2024-02-27 13:53 ` Luis Chamberlain
2024-02-28 12:31 ` John Garry [this message]
2024-02-28 15:18 ` Luis Chamberlain
2024-02-28 16:12 ` John Garry
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=a07db8f8-39f8-44ad-b466-10ac02f3da13@oracle.com \
--to=john.g.garry@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
/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®