From: Christof Schmitt <christof.schmitt@de.ibm.com>
To: FUJITA Tomonori <tomof@acm.org>
Cc: James.Bottomley@HansenPartnership.com,
linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH] zfcp: fix sense_buffer access bug
Date: Mon, 28 Jan 2008 08:46:25 +0100 [thread overview]
Message-ID: <20080128074624.GA4622@schmichrtp.de.ibm.com> (raw)
In-Reply-To: <20080127124124H.tomof@acm.org>
On Sun, Jan 27, 2008 at 12:41:50PM +0900, FUJITA Tomonori wrote:
> The commit de25deb18016f66dcdede165d07654559bb332bc changed
> scsi_cmnd.sense_buffer from a static array to a dynamically allocated
> buffer. We can't access to sense_buffer in '&cmd->sense_buffer' way.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> ---
> drivers/s390/scsi/zfcp_fsf.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/s390/scsi/zfcp_fsf.c b/drivers/s390/scsi/zfcp_fsf.c
> index fe57941..a9a147d 100644
> --- a/drivers/s390/scsi/zfcp_fsf.c
> +++ b/drivers/s390/scsi/zfcp_fsf.c
> @@ -4224,10 +4224,10 @@ zfcp_fsf_send_fcp_command_task_handler(struct zfcp_fsf_req *fsf_req)
>
> ZFCP_LOG_TRACE("%i bytes sense data provided by FCP\n",
> fcp_rsp_iu->fcp_sns_len);
> - memcpy(&scpnt->sense_buffer,
> + memcpy(scpnt->sense_buffer,
> zfcp_get_fcp_sns_info_ptr(fcp_rsp_iu), sns_len);
> ZFCP_HEX_DUMP(ZFCP_LOG_LEVEL_TRACE,
> - (void *) &scpnt->sense_buffer, sns_len);
> + (void *)scpnt->sense_buffer, sns_len);
> }
>
> /* check for overrun */
ACK for fixing the access to the sense buffer.
We are working internally on cleaning up the zfcp messages. With this
change, the 'trace' and 'hex dump' messages will disappear. So, could
you simply remove the ZFCP_HEX_DUMP message above, instead of fixing
it?
Christof
next prev parent reply other threads:[~2008-01-28 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 3:41 [PATCH] zfcp: fix sense_buffer access bug FUJITA Tomonori
2008-01-28 7:46 ` Christof Schmitt [this message]
2008-01-28 9:29 ` FUJITA Tomonori
2008-01-28 10:04 ` Christof Schmitt
2008-01-28 12:53 ` James Bottomley
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=20080128074624.GA4622@schmichrtp.de.ibm.com \
--to=christof.schmitt@de.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=tomof@acm.org \
/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