Date: Fri, 15 May 2020 10:14:24 -0700 From: Chris <bsd-lists@BSDforge.com> To: <arne@Steinkamm.COM> Cc: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, Diane Bruce <db@db.net> Subject: Re: [HEADSUP] Disallowing read() of a directory fd Message-ID: <02cb48c24a3d010dab13974680dc3d16@udns.ultimatedns.net> In-Reply-To: <20200515150627.GY82984@trajan.stk.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 May 2020 17:06:27 +0200 arne@Steinkamm=2ECOM said > On Fri, May 15, 2020 at 10:48:15AM -0400, Diane Bruce wrote: > > All I have to say on this noisy bikeshed is, let's resurrect the mkdir > > bug of V7 because it's tradition and the BSD way and history and stuff=2E > > (I only expect a few of you to remember this one=2E) >=20 > Oh, this "bug" was alive until Sys V 3=2E2 times=2E=2E=2E >=20 > Implementing mkdir as library function without a syscall wasn't a good id= ea=2E > ken and dmr saw no reason to implement mkdir as atomic operation=2E > So it was easy, even with a shell script, to jump between the > mknod(2) and the chown(2) to replace the directory node with a symlink to > /etc/passwd=2E >=20 > This was from a todays point of view a stupid mistake=2E Reading a director= y > node > is lightyears away from "a stupid mistake"=2E >=20 > Make it switchable with a sysctl switch=2E=2E=2E would be the best of both worl= ds=2E So long as it were not read only, might be acceptable=2E But given the potent= ial gains for all this, are trivial at best=2E Why was this proposal not dropped? It's spooling up a massive buffer, for little, to no significant value=2E Move on to something of _actual_ importance -- *please*=2E --Chris >=20 > =2E//=2E Arne >=20 > --=20 > Arne Steinkamm | Home: Mail: arne<at>steinkamm<dot>com > Tel=2E: +49=2E89=2E21031004 | Gr=C3=B6benbachweg 13, 82178 Puchheim, GERMANY
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?02cb48c24a3d010dab13974680dc3d16>