From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Ying Chu <jasonchu@marvell.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/4] mvsas: bugfix for NULL pointer execption
Date: Fri, 08 May 2009 18:05:55 -0400 [thread overview]
Message-ID: <4A04ACC3.4080004@garzik.org> (raw)
In-Reply-To: <1241797393.3327.52.camel@mulgrave.int.hansenpartnership.com>
James Bottomley wrote:
> On Fri, 2009-05-08 at 14:15 +0800, Ying Chu wrote:
>> >From 347191384292c6e9a9a572c657049bc11615fb82 Mon Sep 17 00:00:00 2001
>> From: Andy <ayan@marvell.com>
>> Date: Mon, 4 May 2009 23:29:26 +0800
>> Subject: [PATCH 1/4] mvsas: bug fix, null pointer may be used
>>
>> Null pointer exception when mvi_dev is null.
>
> A little more explanation might be helpful. It looks to me that you get
> this issue when you have in-flight I/O to a device we've been notified
> has gone (because you NULL out lldd_dev in the removal notification
> routine).
>
> In which case, don't we have other races where this can happen, like in
> mvs_I_T_nexus_reset()?
Agreed...
next prev parent reply other threads:[~2009-05-08 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 6:15 [PATCH 1/4] mvsas: bugfix for NULL pointer execption Ying Chu
2009-05-08 15:43 ` James Bottomley
2009-05-08 22:05 ` Jeff Garzik [this message]
2009-05-09 7:26 ` Andy Yan
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=4A04ACC3.4080004@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jasonchu@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox