From: Johannes Thumshirn <jthumshirn@suse.de>
To: Matthew Wilcox <willy@infradead.org>
Cc: YueHaibing <yuehaibing@huawei.com>,
hare@suse.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH -next] advansys: remove set but not used variable 'srb_tag' in adv_isr_callback
Date: Wed, 17 Oct 2018 15:04:54 +0200 [thread overview]
Message-ID: <73b10652-5ccf-4760-4aba-9f58600b6da6@suse.de> (raw)
In-Reply-To: <20181017130022.GA3575@bombadil.infradead.org>
On 17/10/18 15:00, Matthew Wilcox wrote:
> On Wed, Oct 17, 2018 at 02:49:50PM +0200, Johannes Thumshirn wrote:
>> On 17/10/18 14:34, YueHaibing wrote:
>>> - srb_tag = le32_to_cpu(scsiqp->srb_tag);
>>> scp = scsi_host_find_tag(boardp->shost, scsiqp->srb_tag);
>>
>> Shouldn't this be:
>> scp = scsi_host_find_tag(boardp->shost,
>> le32_to_cpu(scsiqp->srb_tag));
>
> I don't think so. Look at how scsiqp->srb_tag is set:
>
> adv_build_req(struct asc_board *boardp, struct scsi_cmnd *scp,
> ADV_SCSI_REQ_Q **adv_scsiqpp)
> {
> + u32 srb_tag = scp->request->tag;
> ...
> + scsiqp->srb_tag = srb_tag;
>
> If we're not converting it to le32 on the way in, we probably don't want
> to convert it back on the way out.
Yeah right, didn't check the submission path. It was just the removed
srb_tag = le32_to_cpu(scsiqp->srb_tag);
that triggered here.
> Please don't make me power up my PA-RISC machine with an Advansys card
> in it, just to find out ...
Now that your saying it...
--
Johannes Thumshirn SUSE Labs
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2018-10-17 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 12:34 YueHaibing
2018-10-17 12:49 ` Johannes Thumshirn
2018-10-17 13:00 ` Matthew Wilcox
2018-10-17 13:04 ` Johannes Thumshirn [this message]
2018-10-18 1:02 ` Martin K. Petersen
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=73b10652-5ccf-4760-4aba-9f58600b6da6@suse.de \
--to=jthumshirn@suse.de \
--cc=hare@suse.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=willy@infradead.org \
--cc=yuehaibing@huawei.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®