From: scameron@beardog.cce.hp.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: james.bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
stephenmcameron@gmail.com, thenzl@redhat.com,
mikem@beardog.cce.hp.com
Subject: Re: [PATCH] hpsa: do not attempt to read from a write-only register
Date: Mon, 11 Jul 2011 16:08:41 -0500 [thread overview]
Message-ID: <20110711210841.GC25366@beardog.cce.hp.com> (raw)
In-Reply-To: <20110711140450.a6f3e8be.akpm@linux-foundation.org>
On Mon, Jul 11, 2011 at 02:04:50PM -0700, Andrew Morton wrote:
> On Mon, 11 Jul 2011 15:51:24 -0500
> scameron@beardog.cce.hp.com wrote:
>
> > On Mon, Jul 11, 2011 at 01:19:11PM -0700, Andrew Morton wrote:
> > > On Fri, 08 Jul 2011 14:59:26 -0500
> > > "Stephen M. Cameron" <scameron@beardog.cce.hp.com> wrote:
> > >
> > > > From: Stephen M. Cameron <scameron@beardog.cce.hp.com>
> > > >
> > > > Most smartarrays tolerate it, but a few new ones don't.
> > > >
> > > > Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com>
> > > > ---
> > > > drivers/scsi/hpsa.h | 2 +-
> > > > 1 files changed, 1 insertions(+), 1 deletions(-)
> > > >
> > > > diff --git a/drivers/scsi/hpsa.h b/drivers/scsi/hpsa.h
> > > > index 6d8dcd4..7f53cea 100644
> > > > --- a/drivers/scsi/hpsa.h
> > > > +++ b/drivers/scsi/hpsa.h
> > > > @@ -214,7 +214,7 @@ static void SA5_submit_command(struct ctlr_info *h,
> > > > dev_dbg(&h->pdev->dev, "Sending %x, tag = %x\n", c->busaddr,
> > > > c->Header.Tag.lower);
> > > > writel(c->busaddr, h->vaddr + SA5_REQUEST_PORT_OFFSET);
> > > > - (void) readl(h->vaddr + SA5_REQUEST_PORT_OFFSET);
> > > > + (void) readl(h->vaddr + SA5_SCRATCHPAD_OFFSET);
> > > > h->commands_outstanding++;
> > > > if (h->commands_outstanding > h->max_outstanding)
> > > > h->max_outstanding = h->commands_outstanding;
> > >
> > > The changelog forgot to tell us the user-visible effects of the bug.
> > > That was really really bad of it. Bad changelog. No bone for you.
> >
> > Oh, sorry. When the controller doesn't tolerate the bug, the firmware
> > on it locks up. No interrupts are received, no commands complete. I/o
> > on that controller grinds to a halt.
>
> OK, that was important.
>
> Presumably you'd like those newer controllers to work with older
> kernels? In which case we should mark the patch for -stable
> backporting?
Yes.
>
> I've done that to my copy and have updated the changelog.
>
> > I can resubmit if you like.
>
> I have two other needed-in-3.0 scsi patches. I'll send all three
> Jameswards now.
next prev parent reply other threads:[~2011-07-11 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 19:59 [PATCH] hpsa: do not attempt to read from a write-only register Stephen M. Cameron
2011-07-11 20:19 ` Andrew Morton
2011-07-11 20:51 ` scameron
2011-07-11 21:04 ` Andrew Morton
2011-07-11 21:08 ` scameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-21 18:16 Stephen M. Cameron
2011-07-21 18:17 ` Stephen Cameron
2011-07-22 22:39 ` Andrew Morton
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=20110711210841.GC25366@beardog.cce.hp.com \
--to=scameron@beardog.cce.hp.com \
--cc=akpm@linux-foundation.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikem@beardog.cce.hp.com \
--cc=stephenmcameron@gmail.com \
--cc=thenzl@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