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: <Zz1tK-rMV5uYyco6@casper.infradead.org>
Date: Wed, 20 Nov 2024 05:01:31 +0000
From: Matthew Wilcox <willy@...radead.org>
To: "wangjianjian (C)" <wangjianjian3@...wei.com>
Cc: Mateusz Guzik <mjguzik@...il.com>, brauner@...nel.org,
	viro@...iv.linux.org.uk, jack@...e.cz, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, hughd@...gle.com,
	linux-ext4@...r.kernel.org, tytso@....edu, linux-mm@...ck.org
Subject: Re: [PATCH v2 1/3] vfs: support caching symlink lengths in inodes

On Wed, Nov 20, 2024 at 12:15:18PM +0800, wangjianjian (C) wrote:
> > +{
> > +	inode->i_link = link;
> > +	inode->i_linklen = linklen;
> Just curious, is this linklen equal to inode size? if it is, why don't use
> it?

Maybe you should read v1 of the patch series where Jan explained where
that's not true.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ