From: Finn Thain <fthain@telegraphics.com.au>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Adaptec OEM Raid Solutions <aacraid@microsemi.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: ips: fix missing break in switch
Date: Wed, 17 Oct 2018 14:24:47 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.21.1810171327290.8@nippy.intranet> (raw)
In-Reply-To: <yq1r2gppdyf.fsf@oracle.com>
On Tue, 16 Oct 2018, Martin K. Petersen wrote:
>
> Finn,
>
> > This looks wrong to me. I think you've just prevented all START STOP
> > commands sent to logical volumes from reaching
> >
> > return ((*ha->func.issue) (ha, scb));
> >
> > I think a better patch is to add a "fall though" comment not a "break"
> > statement. (I no longer have access to a ServeRAID board so I can't
> > test.)
>
> When I looked at this a few days ago, it seemed that the fallthrough to
> the TUR/INQUIRY case statement was accidental and that the intent was to
> quickly complete START_STOP unit (which probably doesn't make much sense
> for a RAID device anyway).
>
> See the case statements above for another fast exit scenario.
>
But that's an error path.
Also note that START_STOP also appears in ips_chkstatus(), which suggests
to me that this command may be submitted legitimately.
> Sadly I have no way to test this. It just stuck out like a false
> positive in Gustavo's fallthrough markup patch.
>
Without testers, and without another maintainer to review this, I'd
advocate a more prudent approach. I wonder whether there is another
maintainer to do a review. The MAINTAINERS file seems to contradict
itself.
$ grep -C5 drivers/scsi/ips MAINTAINERS
...
IBM ServeRAID RAID DRIVER
S: Orphan
F: drivers/scsi/ips.*
...
IPS SCSI RAID DRIVER
M: Adaptec OEM Raid Solutions <aacraid@microsemi.com>
L: linux-scsi@vger.kernel.org
W: http://www.adaptec.com/
S: Maintained
F: drivers/scsi/ips*
...
Note that 'drivers/scsi/ips*' got assigned to Microsemi by a janitorial
change, as part of commit 679655daffdd ("MAINTAINERS - Add file patterns")
in 2009. But for ips.c, the last acked-by from the vendor was in 2008.
--
next prev parent reply other threads:[~2018-10-17 3:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 9:12 Gustavo A. R. Silva
2018-10-16 21:47 ` Martin K. Petersen
2018-10-16 22:27 ` Finn Thain
2018-10-17 1:19 ` Martin K. Petersen
2018-10-17 3:24 ` Finn Thain [this message]
2018-10-18 1:01 ` Martin K. Petersen
2018-10-18 2:37 ` Finn Thain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.21.1810171327290.8@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=aacraid@microsemi.com \
--cc=gustavo@embeddedor.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®