linux-kernel - Re: Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344

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]

Message-Id: <1257262187.3420.73.camel@localhost.localdomain>
Date:	Wed, 04 Nov 2009 00:29:47 +0900
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	David Miller <davem@...emloft.net>,
	torvalds@...ux-foundation.org, linville@...driver.com,
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: Please consider reverting
 7d930bc33653d5592dc386a76a38f39c2e962344

Hi Johannes,

> > > I just think that it's a matter of courtesy that should be independent
> > > from the release cycle to ask the author/maintainer by default, not as a
> > > second thought ("unless [...] have other solution"). You can always CC
> > > Linus and ask him to revert if you don't get a response.
> > > 
> > > What's wrong with that? It doesn't actually delay the action, but it
> > > makes the discussion much more friendly and cooperative instead of
> > > giving the author and maintainer the feeling that their opinion only
> > > matters as a second thought.
> > > 
> > 
> > I think you are reading too much into who was addressed directly and who
> > was "only" CCed... 
> 
> Maybe. But it seems to be happening pretty often recently that people
> first ask for a revert and then for a fix, ignoring any thought that
> might have gone into a particular commit...

I have to agree here. It happens why too often lately. And this needs to
stop. Otherwise why bother with subsystem maintainers? Just send
everything to Linus directly and have him to review every line of code.

Dmitry, this is not against you, but the proper way would have been to
just mail linux-wireless about it and you would have gotten the same
response to it than you got by including Linus and LKML. This blind CC
to LKML is not helpful. It starts confusion and just increases the load
on that mailing list. There is a reason why the MAINTAINERS file now
contains the mailing list contacts, please use them and not try to jump
over two subsystem maintainers to get something fixed. Neither Linus nor
Dave are the right people to comment on your bug.

Regards

Marcel

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