linux-kernel - Re: [PATCH] kobject: fix suppressing modalias in uevents delivered over netlink

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: <CAKdAkRRMFVBGvXJnU0EsQV3j4WRUjPKK6vdG=w5Ft3ruHaObBw@mail.gmail.com>
Date:   Fri, 15 Dec 2017 10:53:10 -0800
From:   Dmitry Torokhov <dmitry.torokhov@...il.com>
To:     Casey Leedom <leedom@...lsio.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Eric Dumazet <eric.dumazet@...il.com>,
        Eric Dumazet <edumazet@...gle.com>,
        Tariq Toukan <tariqt@...lanox.com>,
        "David S . Miller" <davem@...emloft.net>,
        Komali Katari <komali@...lsio.com>,
        "Luis R. Rodriguez" <mcgrof@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kobject: fix suppressing modalias in uevents delivered
 over netlink

On Fri, Dec 15, 2017 at 10:17 AM, Casey Leedom <leedom@...lsio.com> wrote:
> Hi Dmitry,
>
>   Komali reports that she still sees the originally reported issue with your
> latest patch.  This issue started with kernel.org commit
> 1455cf8dbfd06aa7651dcfccbadb7a093944ca65 (Wed Jul 19 17:24:30 2017 -0700).
>
>   cxgb4vf is getting loaded in the Hypervisor when a cxgb4 Virtual Function
> is assigned to a Virtual Machine, and the VM is brought up.  We may need to
> do some debuging ...  How would you like to proceed?

Hmm, can she collect output of 'udevadm monitor -p' at the time you
assign the adapter to the VM? Also, do you have any udev rules that is
specific to cxgb? Or any other custom udev rules?

Also, we only suppress the modalias string on driver unbind, could it
be that for you module loading is happening when driver is bound to
the device? Actually, as far as I can see, you share PCI IDs between
cxgb4 and cxgb4vf drivers, so they have similar modalias entries. How
do you normally decide what driver is to be loaded for a given device?

Thanks.

-- 
Dmitry