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: <2aoxtcshqzrrqfvjs2xger5omq2fjkfifhkdjzvscrtybisca7@eoisrrcki2vw>
Date: Tue, 11 Jun 2024 13:40:37 +0200
From: Mateusz Guzik <mjguzik@...il.com>
To: Jan Kara <jack@...e.cz>
Cc: brauner@...nel.org, viro@...iv.linux.org.uk, 
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-btrfs@...r.kernel.org, 
	josef@...icpanda.com, hch@...radead.org
Subject: Re: [PATCH v3 1/2] vfs: add rcu-based find_inode variants for iget
 ops

On Tue, Jun 11, 2024 at 12:50:11PM +0200, Jan Kara wrote:
> On Tue 11-06-24 12:16:31, Mateusz Guzik wrote:
> > +/**
> > + * ilookup5 - search for an inode in the inode cache
>       ^^^ ilookup5_rcu
> 

fixed in my branch

> > + * @sb:		super block of file system to search
> > + * @hashval:	hash value (usually inode number) to search for
> > + * @test:	callback used for comparisons between inodes
> > + * @data:	opaque data pointer to pass to @test
> > + *
> > + * This is equivalent to ilookup5, except the @test callback must
> > + * tolerate the inode not being stable, including being mid-teardown.
> > + */
> ...
> > +struct inode *ilookup5_nowait_rcu(struct super_block *sb, unsigned long hashval,
> > +		int (*test)(struct inode *, void *), void *data);
> 
> I'd prefer wrapping the above so that it fits into 80 columns.
> 

the last comma is precisely at 80, but i can wrap it if you insist

> Otherwise feel free to add:
> 
> Reviewed-by: Jan Kara <jack@...e.cz>
> 

thanks

I'm going to wait for more feedback, tweak the commit message to stress
that this goes from 2 hash lock acquires to 1, maybe fix some typos and
submit a v4.

past that if people want something faster they are welcome to implement
or carry it over the finish line themselves.

> 									Honza
> -- 
> Jan Kara <jack@...e.com>
> SUSE Labs, CR

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ