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] [day] [month] [year] [list]
Message-ID: <87liv8nrxt.fsf@tucsk.pomaz.szeredi.hu>
Date:	Fri, 05 Aug 2011 11:11:42 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	torvalds@...ux-foundation.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	apw@...onical.com, nbd@...nwrt.org, neilb@...e.de,
	hramrach@...trum.cz, jordipujolp@...il.com, ezk@....cs.sunysb.edu,
	ricwheeler@...il.com, dhowells@...hat.com, hpj@...la.net,
	sedat.dilek@...glemail.com, penberg@...nel.org
Subject: Re: [PATCH 0/8] overlay filesystem: request for inclusion

Al Viro <viro@...IV.linux.org.uk> writes:

> Simple: please, *please* hold back until we have atomic_open mess
> sorted out.  I'm fucking sick and tired of playing whack-a-mole in
> that area - for nearly three years by now; we fortunately are very
> close to getting this shit done right - the main remaining obstacle is
> ->d_revalidate() abuse by NFS and I seriously hope to get it over and
> done with in a week or so.

Sure, that's a totally reasonable thing to ask.

What I ask in return is that you please make your development a bit more
open.

You know it's really annoying when you say something like the above and
then you say it year after year and apparently nothing changes.  If you
could share your work at least we could see what's going on and maybe
even help sort out some of the pieces.  If you are doing it in private,
it looks to be whack-a-mole for years to come.

And I've been asking for this many times, and never got a response.  At
least you could explain why it always has to be a large piece of work
(of excellent quality, btw) suddenly dropped into mainline without
anybody ever seeing any of it previously.

Thanks,
Miklos
--
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