From: Ric Wheeler <rwheeler@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Levy_Jerome@emc.com, linux-scsi@vger.kernel.org,
berthiaume_wayne@emc.com
Subject: Re: [PATCH 1/1] scsi_dh: fix boot oops with EMC Clariion
Date: Fri, 17 Oct 2008 14:37:14 -0400 [thread overview]
Message-ID: <48F8DB5A.1070606@redhat.com> (raw)
In-Reply-To: <1224268412.3368.27.camel@localhost.localdomain>
James Bottomley wrote:
> On Fri, 2008-10-17 at 14:17 -0400, Levy_Jerome@emc.com wrote:
>
>> The change was the addition of rq->flags = 0; the memset isn't mine.
>> Sorry about the whitespace -- I'm still a bit new at this.
>>
>
> That's OK.
>
> Documentation/SubmittingPatches
> Documentation/email-clients.txt
>
> contain useful information.
>
>
>> As to why it's necessary, I've had boot-time oopses on two completely
>> different hosts -- one iSCSI, one FC -- which both resolved to exactly
>> the same code; bizarre values in rq->flags. The source seems to OR the
>> desired values in but never actually initializes rq->flags (the memset
>> initializes the CDB, not the flags variable), so I added the line to
>> do so. After testing the old module to confirm the oops still occurred
>> regularly, I installed the new code and have since (in over 100
>> reboots) been unable to reproduce the oops.
>>
>
> No, my point is that this was fixed by a memset to zero of the request
> in blk_rq_init() in 2.6.26 (so it fixed every other problem, not just
> the one in dm_emc). I think the kernel you're testing is too old to see
> the generic fix (based on what the diff contained).
>
> James
>
Of course, if you see this with a vendor specific (older) kernel, you
can follow up with the vendor and log a bugzilla ticket for that kernel.
Ric
prev parent reply other threads:[~2008-10-17 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 14:46 [PATCH 1/1] scsi_dh: add ALUA notification for EMC Clariion devices Levy_Jerome
2008-09-23 15:57 ` Matthew Wilcox
2008-09-23 16:04 ` Levy_Jerome
2008-10-13 17:41 ` [PATCH 1/1] scsi_dh: fix boot oops with EMC Clariion Levy_Jerome
2008-10-17 17:34 ` James Bottomley
2008-10-17 18:17 ` Levy_Jerome
2008-10-17 18:33 ` James Bottomley
2008-10-17 18:35 ` Levy_Jerome
2008-10-17 18:37 ` Ric Wheeler [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=48F8DB5A.1070606@redhat.com \
--to=rwheeler@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Levy_Jerome@emc.com \
--cc=berthiaume_wayne@emc.com \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.