linux-kernel - Re: [GIT PULL] AFFS update for 6.9

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]

Date: Tue, 12 Mar 2024 13:02:47 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: David Sterba <dsterba@...e.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] AFFS update for 6.9

On Mon, 11 Mar 2024 at 12:37, David Sterba <dsterba@...e.com> wrote:
>
> please pull one change to AFFS that removes use of SLAB_MEM_SPREAD,
> which is going to be removed from MM code.

I've pulled this, but I don't really see the point in removing these
one by one like this.

SLAB_MEM_SPREAD is already a no-op, the MM people could just do a
coccinelle thing to remove it everywhere.

I think you could do 90% even just using a few variations of 'sed', eg
variations on

   git grep -l 'SLAB_MEM_SPREAD' |
        xargs sed -i 's/SLAB_MEM_SPREAD *|//'

   git grep -l 'SLAB_MEM_SPREAD' |
        xargs sed -i 's/| *SLAB_MEM_SPREAD//'

and then some manual fixups for (a) whitespace cleanup of the result
and (b) the couple of cases where it wasn't a bitwise or into other
fields (or where the bitwise or was on a different line)

And then you'd end up with something like the attached.

        Linus

View attachment "patch.diff" of type "text/x-patch" (23779 bytes)