linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Woodhouse, David" <david.woodhouse@intel.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
	"joro@8bytes.org" <joro@8bytes.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"bhe@redhat.com" <bhe@redhat.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"James.Bottomley@hansenpartnership.com"
	<James.Bottomley@hansenpartnership.com>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"scameron@beardog.cce.hp.com" <scameron@beardog.cce.hp.com>
Subject: Re: hpsa driver bug crack kernel down!
Date: Mon, 14 Apr 2014 17:03:51 +0000	[thread overview]
Message-ID: <1397495030.19944.198.camel@shinybook.infradead.org> (raw)
In-Reply-To: <1397494069.31076.9.camel@buesod1.americas.hpqcorp.net>

[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]

On Mon, 2014-04-14 at 09:47 -0700, Davidlohr Bueso wrote:
> On Mon, 2014-04-14 at 09:44 -0700, Davidlohr Bueso wrote:
> > On Tue, 2014-04-15 at 00:19 +0800, Jiang Liu wrote:
> > > Hi Davidlohr,
> > > 	Thanks for providing the DMAR table. According to the DMAR
> > > table, one bug in the iommu driver fails to handle this entry:
> > > [1D2h 0466   1]      Device Scope Entry Type : 01
> > > [1D3h 0467   1]                 Entry Length : 0A
> > > [1D4h 0468   2]                     Reserved : 0000
> > > [1D6h 0470   1]               Enumeration ID : 00
> > > [1D7h 0471   1]               PCI Bus Number : 00
> > > [1D8h 0472   2]                     PCI Path : 1C,04
> > > [1DAh 0474   2]                     PCI Path : 00,02
> > > 
> > > 	And the patch sent out by me should fix this bug. Could you please help
> > > to have a try?
> > 
> > Sorry, I am unable to find any patches from you regarding this issue...
> > I must be missing something. Could you please point me to the lkml link?
> 
> Never mind, I got it internally. I'll let you know  as soon as I can
> test it later today.

Thanks.

Jiang, if you can then let me have a copy with a signed-off-by I'll
shepherd it upstream along with your other patch which is already in my
iommu-2.6.git tree.

-- 
                  Sent with Evolution's ActiveSync support.

David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation





[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3437 bytes --]

  reply	other threads:[~2014-04-14 17:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140409023935.GE11839@dhcp-16-105.nay.redhat.com>
     [not found] ` <1397083799.2608.20.camel@buesod1.americas.hpqcorp.net>
     [not found]   ` <1397084904.9519.62.camel@dabdike>
     [not found]     ` <1397085044.9519.63.camel@dabdike>
     [not found]       ` <1397086817.2608.25.camel@buesod1.americas.hpqcorp.net>
2014-04-09 23:50         ` hpsa driver bug crack kernel down! James Bottomley
2014-04-10  0:19           ` Davidlohr Bueso
2014-04-10  4:03             ` Bjorn Helgaas
2014-04-10  6:32               ` Davidlohr Bueso
2014-04-10  7:15                 ` Joerg Roedel
2014-04-10  8:46                   ` Woodhouse, David
2014-04-10 15:14                     ` Bjorn Helgaas
2014-04-10 15:34                       ` Woodhouse, David
2014-04-10 15:36                       ` Linda Knippers
2014-04-10 16:19                     ` Davidlohr Bueso
2014-04-10 16:30                       ` Woodhouse, David
2014-04-11  9:18                       ` Woodhouse, David
2014-04-14 15:45                         ` Davidlohr Bueso
2014-04-14 16:19                           ` Jiang Liu
2014-04-14 16:44                             ` Davidlohr Bueso
2014-04-14 16:47                               ` Davidlohr Bueso
2014-04-14 17:03                                 ` Woodhouse, David [this message]
2014-04-16 13:37                                   ` joro
2014-04-16 13:58                                     ` Woodhouse, David
2014-04-16 14:13                                       ` joro
2014-04-14  7:01                       ` Jiang Liu
2014-04-14  8:57                       ` Jiang Liu
2014-04-14 18:08                         ` Davidlohr Bueso
2014-04-10 20:45                 ` scameron
2014-04-10 23:17                   ` Shuah Khan
2014-04-11  8:57                     ` David Woodhouse
2014-04-10  8:34               ` Jiang Liu
2014-04-10 15:54                 ` Davidlohr Bueso
2014-04-10 16:02                 ` Davidlohr Bueso
2014-04-11  1:34                 ` Baoquan He
2014-04-11  3:14                 ` Baoquan He

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=1397495030.19944.198.camel@shinybook.infradead.org \
    --to=david.woodhouse@intel.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=bhe@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=davidlohr@hp.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jiang.liu@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scameron@beardog.cce.hp.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;
as well as URLs for NNTP newsgroup(s).