From: Dan Carpenter <dan.carpenter@linaro.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Matthew Brost <matthew.brost@intel.com>,
Tejun Heo <tj@kernel.org>
Cc: open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
linux-block <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>,
Christian Brauner <brauner@kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Christoph Hellwig <hch@lst.de>, Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: next: x86_64: ahci 0000:00:1f.2: probe with driver ahci failed with error -12
Date: Wed, 21 Aug 2024 14:46:22 +0300 [thread overview]
Message-ID: <43be498f-5a25-4ee2-8c5d-1ef75c4d1ff3@stanley.mountain> (raw)
In-Reply-To: <CA+G9fYuYfNA7NZDHpq2K24CsUn21LAb8vn38=JTz=54bsdSd9g@mail.gmail.com>
On Wed, Aug 14, 2024 at 03:56:56PM +0530, Naresh Kamboju wrote:
> On Wed, 14 Aug 2024 at 15:15, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > The qemu-x86_64 boot failed with today's Linux next-20240814 tag due to
> > following crash.
> >
> > The catch here is the crash seen on both x86_64 device and qemu-x86_64
> > but x86_64 device is able to boot successfully.
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > Boot log:
> > ---
> > [ 0.000000] Linux version 6.11.0-rc3-next-20240814
> > (tuxmake@tuxmake) (x86_64-linux-gnu-gcc (Debian 13.3.0-1) 13.3.0, GNU
> > ld (GNU Binutils for Debian) 2.42.50.20240625) #1 SMP PREEMPT_DYNAMIC
> > @1723614704
> > ...
> > <6>[ 2.479915] scsi host0: ahci
> > <4>[ 2.484371] sysfs: cannot create duplicate filename
> > '/devices/virtual/workqueue/scsi_tmf_-1073661392'
^^^^^^^^^^^
Negative number. This comes from:
shost->tmf_work_q = alloc_workqueue("scsi_tmf_%d",
WQ_UNBOUND | WQ_MEM_RECLAIM | WQ_SYSFS,
1, shost->host_no);
shost->host_no comes from ida_alloc() and we have checked to ensure it's not
negative. The problem is the va_args changes in workqueue.c as Anders's bisect
shows.
kernel/workqueue.c
5627 static struct workqueue_struct *__alloc_workqueue(const char *fmt,
5628 unsigned int flags,
5629 int max_active, ...)
^^^
This should be a "va_list args" now.
5750 struct workqueue_struct *alloc_workqueue(const char *fmt,
5751 unsigned int flags,
5752 int max_active, ...)
5753 {
5754 struct workqueue_struct *wq;
5755 va_list args;
5756
5757 va_start(args, max_active);
5758 wq = __alloc_workqueue(fmt, flags, max_active, args);
^^^^
We're passing a va_list.
5759 va_end(args);
Any workqueue that has a format string is going to be broken now.
regards,
dan carpenter
next prev parent reply other threads:[~2024-08-21 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 9:45 Naresh Kamboju
2024-08-14 10:26 ` Naresh Kamboju
2024-08-19 7:49 ` Naresh Kamboju
2024-08-21 11:46 ` Dan Carpenter [this message]
2024-08-21 11:54 ` Dan Carpenter
2024-08-21 13:43 ` Dan Carpenter
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=43be498f-5a25-4ee2-8c5d-1ef75c4d1ff3@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=adobriyan@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=jiangshanlai@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=matthew.brost@intel.com \
--cc=naresh.kamboju@linaro.org \
--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®