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  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:   Thu, 11 Jan 2018 12:01:19 -0500
From:   Theodore Ts'o <>
To:     Kees Cook <>
Cc:, David Windsor <>,
        Andreas Dilger <>,,
        Linus Torvalds <>,
        Alexander Viro <>,
        Andrew Morton <>,
        Andy Lutomirski <>,
        Christoph Hellwig <>,
        Christoph Lameter <>,
        "David S. Miller" <>,
        Laura Abbott <>,
        Mark Rutland <>,
        "Martin K. Petersen" <>,
        Paolo Bonzini <>,
        Christian Borntraeger <>,
        Christoffer Dall <>,
        Dave Kleikamp <>,
        Jan Kara <>,
        Luis de Bethencourt <>,
        Marc Zyngier <>,
        Rik van Riel <>,
        Matthew Garrett <>,,,,,
Subject: Re: [PATCH 13/38] ext4: Define usercopy region in ext4_inode_cache
 slab cache

On Wed, Jan 10, 2018 at 06:02:45PM -0800, Kees Cook wrote:
> The ext4 symlink pathnames, stored in struct ext4_inode_info.i_data
> and therefore contained in the ext4_inode_cache slab cache, need
> to be copied to/from userspace.

Symlink operations to/from userspace aren't common or in the hot path,
and when they are in i_data, limited to at most 60 bytes.  Is it worth
it to copy through a bounce buffer so as to disallow any usercopies
into struct ext4_inode_info?

					- Ted

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux - Powered by OpenVZ