linux-kernel - Re: [PATCH] driver core: Fix test_async_driver

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: <20191209204440.GA1584@roeck-us.net>
Date:   Mon, 9 Dec 2019 12:44:40 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Alexander Duyck <alexander.h.duyck@...ux.intel.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J . Wysocki" <rafael@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] driver core: Fix test_async_driver_probe if NUMA is
 disabled

On Wed, Dec 04, 2019 at 09:18:28AM -0800, Alexander Duyck wrote:
> > 
> > I thought the code is specifically checking devices which it previously
> > created, which are well defined and understood test devices. After all,
> > the check is in the test driver's probe function. Guess I really don't
> > understand the code. Please take my patch as bug report, and submit
> > whatever fix you think is correct.
> 
> Sorry I had overlooked that this is the test code.
> 
> I suppose it should be fine since we specify the node ID for all instances
> where we register an asychronous test device.
> 

That isn't exacly an endorsement. Would you mind submitting a patch
that is acceptable for you ? I'll be more than happy to test it.

Thanks,
Guenter