linux-kernel - Re: [PATCH -vfs] proc: don't maintain sizeof(struct proc_dir

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: <20180518202315.GU30522@ZenIV.linux.org.uk>
Date:   Fri, 18 May 2018 21:23:15 +0100
From:   Al Viro <viro@...IV.linux.org.uk>
To:     Alexey Dobriyan <adobriyan@...il.com>
Cc:     linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        hch@....de
Subject: Re: [PATCH -vfs] proc: don't maintain sizeof(struct proc_dir_entry)

On Fri, May 18, 2018 at 11:02:13PM +0300, Alexey Dobriyan wrote:
> Automatically cap sizeof(struct proc_dir_entry) at 192/128 bytes or
> 256/192 bytes if spinlock debugging/lockdep is enabled.

> --- a/fs/proc/internal.h
> +++ b/fs/proc/internal.h
> @@ -61,13 +61,15 @@ struct proc_dir_entry {
>  	char *name;
>  	umode_t mode;
>  	u8 namelen;
> +	char inline_name[];
> +} __randomize_layout;
> +

Hmm...  proc_root initialization relies upon a gccism after that...
Speaking of which, why the hell do we even bother with proc_root.name?