[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zd3pV7HJEhTjBRz_@bombadil.infradead.org>
Date: Tue, 27 Feb 2024 05:53:27 -0800
From: Luis Chamberlain <mcgrof@...nel.org>
To: John Garry <john.g.garry@...cle.com>
Cc: russ.weight@...ux.dev, gregkh@...uxfoundation.org, rafael@...nel.org,
linux-kernel@...r.kernel.org, masahiroy@...nel.org
Subject: Re: [PATCH] firmware_loader: Use init_utsname()->release
On Tue, Feb 27, 2024 at 05:50:09AM -0800, 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.
I should also mention, kdevops [0] has the linux-firmware selftests and that
has our kernel config used too [1], you can easily build the selftests
and re-retst then manually on the guest. Soon we hope to leverage this
for automation with 0-day so to ensure keep tabs on all of linus'
kernels and linux-next.
If there is anything we should add to our general config it would be
good to add it there.
[0] https://github.com/linux-kdevops/kdevops
[1] https://github.com/linux-kdevops/kdevops/blob/master/playbooks/roles/bootlinux/templates/config-next-202401080
Luis
Powered by blists - more mailing lists