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: <AANLkTin9ac1r_Hur4w=cxkCg2Z-JVYRCwsR6KeZ+9b=R@mail.gmail.com>
Date:	Thu, 13 Jan 2011 13:14:14 +1100
From:	Nick Piggin <npiggin@...il.com>
To:	Ian Kent <raven@...maw.net>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>, aelder@....com,
	Nick Piggin <npiggin@...nel.dk>,
	Al Viro <viro@...iv.linux.org.uk>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [announce] vfs-scale git tree update

On Thu, Jan 13, 2011 at 12:48 PM, Ian Kent <raven@...maw.net> wrote:
> On Thu, 2011-01-13 at 12:01 +1100, Nick Piggin wrote:
>> Hm, what are the concurrencies that you need protection from?
>
> Ha, I think I'm wrong about this, after looking more closely at this I'm
> struggling to see why autofs4_lock is needed at all.

Well you did send me a series of patches to remove it, but
unfortunately that was just as you made some larger changes
to autofs4 upstream and I wasn't able to keep them up to date.

It would be much appreciated if you had time to take another
look at all the locking and streamline it.

Thanks,
Nick
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ