linux-kernel - Re: [take2] Inotify: nested attributes support.

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]

Date:	Wed, 26 Nov 2008 16:15:39 +0300
From:	Evgeniy Polyakov <zbr@...emap.net>
To:	David Newall <davidn@...idnewall.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, john@...nmccutchan.com,
	arnd@...db.de, mtk.manpages@...il.com, hch@....de, rlove@...ve.org,
	linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
	pavel@...e.cz, Eric Paris <eparis@...hat.com>
Subject: Re: [take2] Inotify: nested attributes support.

On Wed, Nov 26, 2008 at 11:33:35PM +1030, David Newall (davidn@...idnewall.com) wrote:
> > And as was shown it does not work for all cases and introduces unneded
> > performance overhead.
> 
> If the performance using a local loopback is insufficient, or even when
> using a UNIX domain socket, then it's going to be even worse for the
> actual network-connected clients.  And the cases were it doesn't work
> amount to poor system administration, which is a solvable problem.

Proposing to introduce additional overhead when it can be avoided is not
the best way to deal with the problem.
Another small detail, that it does not completely solve the problem.

> >> This change violates my first rule of programming: If there's two or
> >> more ways of solving a problem, pick one; don't pick them all.
> >
> > Then we should go back to caves, raw meat was so tasty...
> 
> Amusing, but irrelevant to programming.

Programming is so special, that new things which help having a progress
should not be developed there? Care to recall how to work with the punch
card? Following your logic inotify should be returned from the kernel,
since all applications which may do IO can be modified to first register
it in some special database and not checking IO at run-time. And we will
not care about others who did not do that.

Your 'rule' does not apply to the case, where is no way to solve the
problem completely using existing methods.

-- 
	Evgeniy Polyakov
--
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/