lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <c2702c969f01f9dcf2d6b3d3326e804c3fee86c0.camel@linux.ibm.com> Date: Wed, 31 May 2023 15:43:15 +0200 From: Niklas Schnelle <schnelle@...ux.ibm.com> To: Linux regressions mailing list <regressions@...ts.linux.dev>, Shay Drory <shayd@...dia.com>, Saeed Mahameed <saeedm@...dia.com>, Eli Cohen <elic@...dia.com>, netdev@...r.kernel.org Subject: Re: mlx5 driver is broken when pci_msix_can_alloc_dyn() is false with v6.4-rc4 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@...dia.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
Powered by blists - more mailing lists