linux-kernel - Re: [PATCH] cciss: fix incorrect scsi status reporting

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] [day] [month] [year] [list]

Message-ID: <CADzpL0Qs_4SZeR-E_TCnagQQwNR3OC_ncOGZpGS62dNPtCwfdw@mail.gmail.com>
Date:	Wed, 9 May 2012 18:21:37 -0500
From:	Stephen Cameron <stephenmcameron@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	"Stephen M. Cameron" <scameron@...rdog.cce.hp.com>,
	axboe@...nel.dk, mikem@...rdog.cce.hp.com,
	linux-kernel@...r.kernel.org, thenzl@...hat.com,
	roel.vanmeer@...xing.nl
Subject: Re: [PATCH] cciss: fix incorrect scsi status reporting

On Wed, May 9, 2012 at 4:59 PM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Fri, 04 May 2012 13:21:14 -0500
> "Stephen M. Cameron" <scameron@...rdog.cce.hp.com> wrote:
>
>> From: Stephen M. Cameron <scameron@...rdog.cce.hp.com>
>>
>> Delete code which sets SCSI status incorrectly as it's already
>> been set correctly above this incorrect code.  Bug was introduced
>> by b0e15f6db1110319cb2e747e59e1200450a5ba3e
>> "cciss: fix typo that causes scsi status to be lost." in 2009.
>>
>> Signed-off-by: Stephen M. Cameron <scameron@...rdog.cce.hp.com>
>> Reported-and-tested-by: Roel van Meer <roel.vanmeer@...xing.nl>
>> Cc: stable@...r.kernel.org
>
> If the bug is three years old, it presumably isn't a terribly serious
> one.  Why was the -stable backport recommended?

(added roel.vanmeer@...xing.nl to cc list)

Due to my subjective interpretation of stable_kernel_rules.txt,
specifically this part:

 - It must fix a problem that causes a build error (but not for things
   marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
   security issue, or some "oh, that's not good" issue.  In short, something
   critical.

I thought it fell under the "oh, that's not good", in that, according
to the tester, iirc, it made his tape drive not show up at all, which
seemed bad (though not a symptom I observed directly), and it seemed
like a trivial fix to something obviously incorrect, so thought stable
might like to know about it.  But, maybe not.

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