linux-kernel - Re: [GIT PATCH] intermediate SCSI updates

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, 13 Oct 2008 14:22:13 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PATCH] intermediate SCSI updates

On Mon, 13 Oct 2008, James Bottomley wrote:
> 
> Not exactly.  It has to be rebased to run as a postmerge tree, but it
> does get tested by me (admittedly on my limited set of machines, which
> don't include any actual devices that do block integrity) every time I
> rebase.

What I'm upset about is that this has apparently gotten not even some 
trivial testing of the _default_ build. I'm not talking about any odd 
config options here. I'm literally talking about the only _sane_ config 
option case.

You yourself admit that even you don't have any actual devices that can 
support the block integrity stuff, yet you have apparently only compile- 
tested the insane case of still enabling that thing and apparently nobody 
else has bothered either.

Was this in linux-next?

Is linux-next coverage REALLY so weak that it doesn't even test the 
default config options, much less any random options? What's the point of 
linux-next then?

Again, the date on that thing is claimed to be September 19th, although it 
was obviously committed later.

> However, does this work for you?  It fixes the problem for me.

I could trivially have fixed the compile issue. That's not what upsets me. 
What upsets me is that this set of patches apparently had almost nobody 
looking at them at all before they got sent to me.

If it was some odd and unusual config option, I'd be less upset. hey, 
stuff happens. But it sure as heck was nothing of the sort!

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