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: <ea6708ce-af4a-4f0a-ba37-a2cb38f60eca@nvidia.com>
Date:   Wed, 13 Dec 2023 14:01:32 -0800
From:   John Hubbard <jhubbard@...dia.com>
To:     David Hildenbrand <david@...hat.com>,
        Muhammad Usama Anjum <usama.anjum@...labora.com>,
        Mark Brown <broonie@...nel.org>
CC:     Suren Baghdasaryan <surenb@...gle.com>,
        <akpm@...ux-foundation.org>, <viro@...iv.linux.org.uk>,
        <brauner@...nel.org>, <shuah@...nel.org>, <aarcange@...hat.com>,
        <lokeshgidra@...gle.com>, <peterx@...hat.com>,
        <ryan.roberts@....com>, <hughd@...gle.com>, <mhocko@...e.com>,
        <axelrasmussen@...gle.com>, <rppt@...nel.org>,
        <willy@...radead.org>, <Liam.Howlett@...cle.com>,
        <jannh@...gle.com>, <zhangpeng362@...wei.com>,
        <bgeffon@...gle.com>, <kaleshsingh@...gle.com>,
        <ngeoffray@...gle.com>, <jdduke@...gle.com>, <linux-mm@...ck.org>,
        <linux-fsdevel@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-kselftest@...r.kernel.org>, <kernel-team@...roid.com>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v6 5/5] selftests/mm: add UFFDIO_MOVE ioctl test

On 12/13/23 01:59, David Hildenbrand wrote:
...
>> Another variation though, would be to run "make headers", and snapshot
>> some of those files into tools/include.
> 
> ^ this is what I had in mind
> 
> If you're writing a test that needs some new fancy thing, update the relevant header.
> 

OK, and Mark Brown's nearby response [1] supports that, as well.

Thus fortified, I plan on doing the following steps:

Step 1: Do nothing about the revert patch that I sent earlier, thus
allowing it to continue in its journey (so far, Andrew has moved it into
mm-hotfixes-stable branch).

Step 2: Send out a patch for a modest part of selftests/mm, that uses
this latest approach, and see how it fares in reviews.

[1] https://lore.kernel.org/c0aa00a2-38a5-42da-9951-64131d936f7e@sirena.org.uk


thanks,
-- 
John Hubbard
NVIDIA

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ