From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Niklas Schnelle <schnelle@linux.ibm.com>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Shay Drory <shayd@nvidia.com>, Saeed Mahameed <saeedm@nvidia.com>,
Eli Cohen <elic@nvidia.com>,
netdev@vger.kernel.org
Subject: Re: mlx5 driver is broken when pci_msix_can_alloc_dyn() is false with v6.4-rc4
Date: Wed, 31 May 2023 15:57:14 +0200 [thread overview]
Message-ID: <ab31715a-0fe7-f881-be1a-2b69fde82f23@leemhuis.info> (raw)
In-Reply-To: <c2702c969f01f9dcf2d6b3d3326e804c3fee86c0.camel@linux.ibm.com>
On 31.05.23 15:43, Niklas Schnelle wrote:
> On Wed, 2023-05-31 at 15:33 +0200, Linux regression tracking #adding
> (Thorsten Leemhuis) wrote:
>> [CCing the regression list, as it should be in the loop for regressions:
>> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>>
>> [TLDR: I'm adding this report to the list of tracked Linux kernel
>> regressions; the text you find below is based on a few templates
>> paragraphs you might have encountered already in similar form.
>> See link in footer if these mails annoy you.]
>>
>> On 30.05.23 15:04, Niklas Schnelle wrote:
>>>
>>> With v6.4-rc4 I'm getting a stream of RX and TX timeouts when trying to
>>> use ConnectX-4 and ConnectX-6 VFs on s390. I've bisected this and found
>>> the following commit to be broken:
>>>
>>> commit 1da438c0ae02396dc5018b63237492cb5908608d
>>> Author: Shay Drory <shayd@nvidia.com>
>>> Date: Mon Apr 17 10:57:50 2023 +0300
>>> [...]
>>
>> Thanks for the report. To be sure the issue doesn't fall through the
>> cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
>> tracking bot:
>>
>> #regzbot ^introduced 1da438c0ae02396dc5018b63237492cb5908608d
>> #regzbot title net/mlx5: RX and TX timeouts with ConnectX-4 and
>> ConnectX-6 VFs on s390
>> #regzbot ignore-activity
>>
>> This isn't a regression? This issue or a fix for it are already
>> discussed somewhere else? It was fixed already? You want to clarify when
>> the regression started to happen? Or point out I got the title or
>> something else totally wrong? Then just reply and tell me -- ideally
>> while also telling regzbot about it, as explained by the page listed in
>> the footer of this mail.
>>
>> Developers: When fixing the issue, remember to add 'Link:' tags pointing
>> to the report (the parent of this mail). See page linked in footer for
>> details.
>>
>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>> --
>> Everything you wanna know about Linux kernel regression tracking:
>> https://linux-regtracking.leemhuis.info/about/#tldr
>> That page also explains what to do if mails like this annoy you.
>
> Hi Thorsten,
>
> Thanks for tracking. I actually already sent a fix patch (and v2) for
> this. Sadly I forgot to link to this mail. Let's see if I can get the
> regzbot command right to update it. As for the humans the latest fix
> patch is here:
>
> https://lore.kernel.org/netdev/20230531084856.2091666-1-schnelle@linux.ibm.com/
>
> Thanks,
> Niklas
>
> #regzbot fix: net/mlx5: Fix setting of irq->map.index for static IRQ case
Looks right, many thx. Sorry, should have looked for that myself. Sadly
regzbot doesn't yet search for existing post on lore with a matching
subject, so for completeness let me point manually to it while at it:
#regzbot monitor:
https://lore.kernel.org/netdev/20230531084856.2091666-1-schnelle@linux.ibm.com/
Ciao, Thorsten
next prev parent reply other threads:[~2023-05-31 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 13:04 mlx5 driver is broken when pci_msix_can_alloc_dyn() is false with v6.4-rc4 Niklas Schnelle
2023-05-31 13:33 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-05-31 13:43 ` Niklas Schnelle
2023-05-31 13:57 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-05-31 21:48 ` Saeed Mahameed
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=ab31715a-0fe7-f881-be1a-2b69fde82f23@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=elic@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=saeedm@nvidia.com \
--cc=schnelle@linux.ibm.com \
--cc=shayd@nvidia.com \
/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).