linux-kernel - Re: [GIT pull] irq/core for v5.17-rc1

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=whvPxG2Sje_OBSeDODiD68ke+ta118xeYskNxkv-kAtyA@mail.gmail.com>
Date:   Thu, 13 Jan 2022 09:01:23 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Saeed Mahameed <saeedm@...dia.com>,
        Leon Romanovsky <leon@...nel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Ingo Molnar <mingo@...nel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: [GIT pull] irq/core for v5.17-rc1

On Thu, Jan 13, 2022 at 2:13 AM Thomas Gleixner <tglx@...utronix.de> wrote:
>
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-core-2022-01-13

Hmm.

I got a conflict in the mlx driver. It looked trivial, but just to
make sure I compared against the resolution in linux-next.

My conflict resolution is different, though, and I think mine is the
correct one (although maybe they end up both being fine).

But I'm just about to leave for travel, and maybe I'm wrong, so I just
wanted to people to verify...

It's

   drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c

and in particular the 'err_xa' release part of mlx5_irq_alloc() - I
made it use irq_update_affinity_hint() to match the irq_release()
paths.

Maybe irq_set_affinity_hint() is equivalent when the new hint is NULL?

            Linus