linux-kernel - Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion

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:	Mon, 24 Jul 2006 19:50:55 +0200
From:	Olivier Galibert <galibert@...ox.com>
To:	Theodore Tso <tytso@....edu>,
	Linux Kernel Mailing List <Linux-Kernel@...r.kernel.org>,
	Nikita Danilov <nikita@...sterfs.com>,
	Steve Lord <lord@....org>
Subject: Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion

On Mon, Jul 24, 2006 at 12:17:55PM -0400, Theodore Tso wrote:
> I would also note that we didn't intimate that we knew better than the
> reviewers, or question their motives, or otherwise insult the
> reviewers such that they might decide they have better things to do
> than to review our patches, and that might have had something to do
> with how the code got in relatively painlessly....

Now that has a very high impact :-) Hans is not very good at the
diplomacy game.

The fact that the ext maintainers are very, very good helps quite a
lot too.  But I think it doesn't change the fact that if r4 has been a
set of patches through time to r3, good or not, there wouldn't be a
discussion.

It's maybe the lack of an official development branch, but it looks
like the kernel development has become very risk-averse, and the bar
is set much higher to accept anything that looks relatively new.  Any
reason is good to have it dropped, cosmetic or not.

Just to give you an idea, if the criteria applied to suspend2 or
reiser4 had been applied to everything else, we wouldn't have at least
XFS[1], ALSA[2], sysfs[3] and DRM[4].  Whether it is good or bad is an
interesting question itself.  But before, code just had to be
reasonably sane, and it was expected to be fixed through time.  Some
even has been (sysfs got better).  Now it has to attain an ever moving
level of perfection before it has a chanc to be accepted.

Unless you're a maintainer, that is, for which you can get pretty much
anything in that doesn't immediatly break the compile through git
trees.  Thankfully, most of the maintainers are sane.

Don't you think this is a problem?

  OG.

[1] CodingStyle is for the weak

[2] You call that a kernel interface?  HWDEP?  ioctl to read/write
    samples instead of read/write?

[3] Lifetime rules and locking are for other people to care about

[4] Oh my, people are still trying to fix that one
-
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/