[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zhx2PfHjjTmjBZY8@casper.infradead.org>
Date: Mon, 15 Apr 2024 01:35:09 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Alexey Dobriyan <adobriyan@...il.com>
Cc: Luis Chamberlain <mcgrof@...nel.org>, akpm@...ux-foundation.org,
linux-modules@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, viro@...iv.linux.org.uk,
brauner@...nel.org, jack@...e.cz
Subject: Re: [PATCH] module: ban '.', '..' as module names, ban '/' in module
names
On Sun, Apr 14, 2024 at 10:05:05PM +0300, Alexey Dobriyan wrote:
> Any other subsystem should use nice helper function aptly named
>
> string_is_vfs_ready()
>
> and apply additional restrictions if necessary.
>
> /proc/modules hints that newlines should be banned too,
> and \x1f, and whitespace, and similar looking characters
> from different languages and emojis (except 🐧obviously).
I don't see the purpose of allowing any character in 0x01-0x1f.
How annoying to have BEL in there. And, really, what's the value in
allowing characters after 0x7e?
Powered by blists - more mailing lists