Date: Wed, 10 Mar 2004 16:38:55 -0500 From: "Brian F. Feldman" <green@FreeBSD.org> To: "Poul-Henning Kamp" <phk@phk.freebsd.dk> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sys mdioctl.h src/sys/dev/md md.c src/sbin/mdconfig mdconfig.8 mdconfig.c Message-ID: <200403102138.i2ALcuYj073417@green.homeunix.org> In-Reply-To: Message from "Poul-Henning Kamp" <phk@phk.freebsd.dk> <44707.1078953312@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
"Poul-Henning Kamp" <phk@phk.freebsd.dk> wrote: > In message <200403102109.i2AL96dn073169@green.homeunix.org>, "Brian F. Feldman" > writes: > > >Could you please implement an errx(3) for MD_ASYNC without MD_FORCE, or > >something of that ilk? Users who use anything other than mdconfig(8) for > >leanring how to use mdconfig(8) could quite easily run across something like: > > "Make sure to use -o async to get better performance." > >and shoot themselves in the foot, whereas if they saw: > > "Make sure to use -o force -o async..." > > mdconfig(8) is plenty dangerous as it is, obfuscating the arguments > is not an improvement for the marginal extra protection. Please inform me what makes mdconfig(8) dangerous when operating on a vnode. If the only thing that can be said is "-o async may cause deadlocks," then this is not "marginal extra protection" against a mode of operation that should, except for use of this option, cause no instability. Do you believe that the average hacker will think "o async, that actually sounds dangerous... maybe I should look it up first?" -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403102138.i2ALcuYj073417>