From: Christoph Hellwig <hch@lst.de>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
hch@lst.de, tcallawa@redhat.com
Subject: Re: [PATCH]: Fix scsi_send_eh_cmnd scatterlist handling
Date: Mon, 2 Apr 2007 21:29:40 +0200 [thread overview]
Message-ID: <20070402192940.GA6644@lst.de> (raw)
In-Reply-To: <20070402.122439.71098419.davem@davemloft.net>
On Mon, Apr 02, 2007 at 12:24:39PM -0700, David Miller wrote:
>
> This fixes a regression caused by commit:
>
> 2dc611de5a3fd955cd0298c50691d4c05046db97
>
> The sense buffer code in scsi_send_eh_cmnd was changed to use
> alloc_page() and a scatter list, but the sense data copy was not
> updated to match so what we actually get in the sense buffer is total
> grabage starting with the kernel address of the struct page we got.
> Basically the stack frame of scsi_send_eh_cmd() is what ends up
> in the sense buffer.
>
> Depending upon how pointers look on a given platform, you can
> end up getting sr_ioctl.c errors when you mount a cdrom. If
> the CDROM gives a check condition for GPCMD_GET_CONFIGURATION issued
> by drivers/cdrom/cdrom.c:cdrom_mmc_profile(), sr_ioctl will
> spit out this error message in sr_do_ioctl() with the way pointers
> are on sparc64:
>
> default:
> printk(KERN_ERR "%s: CDROM (ioctl) error, command: ", cd->cdi.name);
> __scsi_print_command(cgc->cmd);
> scsi_print_sense_hdr("sr", &sshdr);
> err = -EIO;
>
> This is the error Tom Callaway reported in:
>
> http://marc.info/?l=linux-sparc&m=117407453208101&w=2
>
> Anyways, fix this by using page_address(sgl.page) which is OK
> because we know this is low-mem due to GFP_ATOMIC.
The patch looks correct to me and thanks for spotting this stupid
bug!
prev parent reply other threads:[~2007-04-02 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 19:24 [PATCH]: Fix scsi_send_eh_cmnd scatterlist handling David Miller
2007-04-02 19:29 ` Christoph Hellwig [this message]
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=20070402192940.GA6644@lst.de \
--to=hch@lst.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tcallawa@redhat.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