From: Marc Zyngier <maz@kernel.org>
To: Barry Song <21cnbao@gmail.com>
Cc: kernel test robot <oliver.sang@intel.com>,
0day robot <lkp@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Barry Song <song.bao.hua@hisilicon.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jonathan.Cameron@huawei.com, bilbao@vt.edu,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
leon@kernel.org, linux-pci@vger.kernel.org,
Linuxarm <linuxarm@huawei.com>,
luzmaximilian@gmail.com, mchehab+huawei@kernel.org,
schnelle@linux.ibm.com, intel-wired-lan@lists.osuosl.org
Subject: Re: [PCI/MSI] a4fc4cf388: dmesg.genirq:Flags_mismatch_irq##(mei_me)vs.#(xhci_hcd)
Date: Tue, 31 Aug 2021 09:08:06 +0100 [thread overview]
Message-ID: <1132a536516f15ab6b338ab868ec3705@kernel.org> (raw)
In-Reply-To: <CAGsJ_4yYwjuWsEeK3CvnOhc10mbBNYWXqxqp+mR5587R2FD3gQ@mail.gmail.com>
On 2021-08-31 02:21, Barry Song wrote:
> On Mon, Aug 30, 2021 at 2:38 AM kernel test robot
> <oliver.sang@intel.com> wrote:
>>
>>
>>
>> Greeting,
>>
>> FYI, we noticed the following commit (built with gcc-9):
>>
>> commit: a4fc4cf388319ea957ffbdab5073bdd267de9082 ("[PATCH v3 3/3]
>> PCI/MSI: remove msi_attrib.default_irq in msi_desc")
>> url:
>> https://github.com/0day-ci/linux/commits/Barry-Song/PCI-MSI-Clarify-the-IRQ-sysfs-ABI-for-PCI-devices/20210825-183018
>> base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
>> 6e764bcd1cf72a2846c0e53d3975a09b242c04c9
>>
>> in testcase: kernel-selftests
>> version: kernel-selftests-x86_64-ebaa603b-1_20210825
>> with following parameters:
>>
>> group: pidfd
>> ucode: 0xe2
>>
>> test-description: The kernel contains a set of "self tests" under the
>> tools/testing/selftests/ directory. These are intended to be small
>> unit tests to exercise individual code paths in the kernel.
>> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>>
>>
>> on test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
>> with 32G memory
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire
>> log/backtrace):
>>
>>
>>
>> If you fix the issue, kindly add following tag
>> Reported-by: kernel test robot <oliver.sang@intel.com>
>>
>>
>>
>> [ 179.602028][ T34] genirq: Flags mismatch irq 16. 00002000
>> (mei_me) vs. 00000000 (xhci_hcd)
>> [ 179.614073][ T34] CPU: 2 PID: 34 Comm: kworker/u8:2 Not tainted
>> 5.14.0-rc7-00014-ga4fc4cf38831 #1
>> [ 179.623225][ T34] Hardware name: Dell Inc. OptiPlex 7040/0Y7WYT,
>> BIOS 1.8.1 12/05/2017
>> [ 179.631432][ T34] Workqueue: events_unbound async_run_entry_fn
>> [ 179.637543][ T34] Call Trace:
>> [ 179.640789][ T34] dump_stack_lvl+0x45/0x59
>> [ 179.645253][ T34] __setup_irq.cold+0x50/0xd4
>> [ 179.649893][ T34] ? mei_me_pg_exit_sync+0x480/0x480 [mei_me]
>> [ 179.655923][ T34] request_threaded_irq+0x10c/0x180
>> [ 179.661073][ T34] ? mei_me_irq_quick_handler+0x240/0x240
>> [mei_me]
>> [ 179.667528][ T34] mei_me_probe+0x131/0x300 [mei_me]
>> [ 179.672767][ T34] local_pci_probe+0x42/0x80
>> [ 179.677313][ T34] pci_device_probe+0x107/0x1c0
>> [ 179.682118][ T34] really_probe+0xb6/0x380
>> [ 179.687094][ T34] __driver_probe_device+0xfe/0x180
>> [ 179.692242][ T34] driver_probe_device+0x1e/0xc0
>> [ 179.697133][ T34] __driver_attach_async_helper+0x2b/0x80
>> [ 179.702802][ T34] async_run_entry_fn+0x30/0x140
>> [ 179.707693][ T34] process_one_work+0x274/0x5c0
>> [ 179.712503][ T34] worker_thread+0x50/0x3c0
>> [ 179.716959][ T34] ? process_one_work+0x5c0/0x5c0
>> [ 179.721936][ T34] kthread+0x14f/0x180
>> [ 179.725958][ T34] ? set_kthread_struct+0x40/0x40
>> [ 179.730935][ T34] ret_from_fork+0x22/0x30
>> [ 179.735699][ T34] mei_me 0000:00:16.0: request_threaded_irq
>> failure. irq = 16
>> [ 179.743125][ T34] mei_me 0000:00:16.0: initialization failed.
>> [ 179.749399][ T34] mei_me: probe of 0000:00:16.0 failed with error
>> -16
>>
>>
>
> it seems there is a direct reference to pdev->irq.
> Hi Oliver, would you try if the below patch can fix the problem:
>
> diff --git a/drivers/misc/mei/pci-me.c b/drivers/misc/mei/pci-me.c
> index c3393b383e59..a45a2d4257a6 100644
> --- a/drivers/misc/mei/pci-me.c
> +++ b/drivers/misc/mei/pci-me.c
> @@ -216,7 +216,7 @@ static int mei_me_probe(struct pci_dev *pdev,
> const struct pci_device_id *ent)
>
> pci_enable_msi(pdev);
>
> - hw->irq = pdev->irq;
> + hw->irq = pci_irq_vector(pdev, 0);
>
> /* request and enable interrupt */
> irqflags = pci_dev_msi_enabled(pdev) ? IRQF_ONESHOT :
> IRQF_SHARED;
>
Ah! one victim, 3000 to go! :D
That's exactly the kind of stuff I was mentioning when we
discussed this patch. Exposing the MSI vector as the INTx
IRQ has led to all sorts of broken drivers.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2021-08-31 8:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 10:26 [PATCH v3 0/3] PCI/MSI: Clarify the IRQ sysfs ABI for PCI devices Barry Song
2021-08-25 10:26 ` [PATCH v3 1/3] Documentation: ABI: sysfs-bus-pci: Add description for IRQ entry Barry Song
2021-08-25 10:26 ` [PATCH v3 2/3] PCI/sysfs: Don't depend on pci_dev.irq " Barry Song
2021-08-25 13:30 ` Marc Zyngier
2021-08-25 10:26 ` [PATCH v3 3/3] PCI/MSI: remove msi_attrib.default_irq in msi_desc Barry Song
2021-08-25 13:38 ` Marc Zyngier
[not found] ` <20210829145552.GA11556@xsang-OptiPlex-9020>
2021-08-31 1:21 ` [PCI/MSI] a4fc4cf388: dmesg.genirq:Flags_mismatch_irq##(mei_me)vs.#(xhci_hcd) Barry Song
2021-08-31 1:36 ` Barry Song
2021-09-02 19:34 ` Winkler, Tomas
2021-10-03 8:32 ` Barry Song
[not found] ` <20211015144528.GA21175@linux.intel.com>
2021-10-16 0:08 ` [LKP] " Barry Song
2021-08-31 8:08 ` Marc Zyngier [this message]
2021-08-31 21:36 ` Barry Song
2021-09-01 13:09 ` Marc Zyngier
2021-10-16 10:11 ` [PATCH v3 0/3] PCI/MSI: Clarify the IRQ sysfs ABI for PCI devices Barry Song
2021-10-18 21:50 ` Bjorn Helgaas
2021-10-19 7:39 ` Marc Zyngier
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=1132a536516f15ab6b338ab868ec3705@kernel.org \
--to=maz@kernel.org \
--cc=21cnbao@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bhelgaas@google.com \
--cc=bilbao@vt.edu \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=luzmaximilian@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=oliver.sang@intel.com \
--cc=schnelle@linux.ibm.com \
--cc=song.bao.hua@hisilicon.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).