netdev - RE: [PATCH net-next] liquidio: use meaningful names for IRQs

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: <BL2PR07MB2306BA618DA5459D7BADFC838D3A0@BL2PR07MB2306.namprd07.prod.outlook.com>
Date:   Mon, 20 Mar 2017 08:26:08 +0000
From:   "Mintz, Yuval" <Yuval.Mintz@...ium.com>
To:     David Miller <davem@...emloft.net>,
        "Manlunas, Felix" <Felix.Manlunas@...ium.com>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "Vatsavayi, Raghu" <Raghu.Vatsavayi@...ium.com>,
        "Chickles, Derek" <Derek.Chickles@...ium.com>,
        "Burla, Satananda" <Satananda.Burla@...ium.com>,
        Ricardo Farrington <Ricardo.Farrington@...ium.com>
Subject: RE: [PATCH net-next] liquidio: use meaningful names for IRQs

> >     2.  The IRQ name can only be specified at the time it is requested.
> >         It cannot be changed after that.

Is there any inherent difficulty in adding that capability?
I.e., to rename the IRQ's action & kthread.

It would allow drivers to re-name their IRQ names upon NETDEV_CHANGENAME.