From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: arcmsr + archttp64 calls dma_free_coherent() with irqs disabled - dmesg filled with warnings Date: Fri, 15 Feb 2008 15:57:23 -0600 Message-ID: <1203112643.3058.48.camel@localhost.localdomain> References: <47ADC74B.9080009@control.aau.dk> <1202580076.4254.24.camel@localhost.localdomain> <20080209193518.GC11299@hoblitt.com> <1202586219.4254.35.camel@localhost.localdomain> <20080212205345.GB7640@hoblitt.com> <20080212222109.GC7640@hoblitt.com> <1202855436.3137.153.camel@localhost.localdomain> <20080215205657.GB23625@hoblitt.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from accolon.hansenpartnership.com ([76.243.235.52]:47316 "EHLO accolon.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754571AbYBOV5d (ORCPT ); Fri, 15 Feb 2008 16:57:33 -0500 In-Reply-To: <20080215205657.GB23625@hoblitt.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Joshua Hoblitt Cc: Kim H?jgaard-Hansen , erich@areca.com.tw, linux-scsi@vger.kernel.org, dsd@gentoo.org, j_gentoo@hoblitt.com On Fri, 2008-02-15 at 10:56 -1000, Joshua Hoblitt wrote: > Hi James, > > Daniel took the time to patch up the 2.6.24 version. I've tested it and > the warning messages are gone. Please take a look at: > > diff --git a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c > index f4a202e..4f9ff32 100644 > --- a/drivers/scsi/arcmsr/arcmsr_hba.c > +++ b/drivers/scsi/arcmsr/arcmsr_hba.c > @@ -1380,12 +1388,13 @@ static int arcmsr_iop_message_xfer(struct AdapterControlBlock *acb, \ > > case ARCMSR_MESSAGE_READ_RQBUFFER: { > unsigned long *ver_addr; > - dma_addr_t buf_handle; > uint8_t *pQbuffer, *ptmpQbuffer; > int32_t allxfer_len = 0; > + void *tmp; > > - ver_addr = pci_alloc_consistent(acb->pdev, 1032, &buf_handle); > - if (!ver_addr) { > + tmp = kmalloc(1032, GFP_KERNEL|GFP_DMA); GFP_DMA is pretty pointless for a buffer which never actually gets anywhere near a DMA, isn't it? > + ver_addr = (unsigned long *)tmp; No cast needed from void * > + if (!tmp) { > retvalue = ARCMSR_MESSAGE_FAIL; > goto message_out; > } > @@ -1421,18 +1430,19 @@ static int arcmsr_iop_message_xfer(struct AdapterControlBlock *acb, \ > memcpy(pcmdmessagefld->messagedatabuffer, (uint8_t *)ver_addr, allxfer_len); > pcmdmessagefld->cmdmessage.Length = allxfer_len; > pcmdmessagefld->cmdmessage.ReturnCode = ARCMSR_MESSAGE_RETURNCODE_OK; > - pci_free_consistent(acb->pdev, 1032, ver_addr, buf_handle); > + kfree(tmp); > } > break; > > case ARCMSR_MESSAGE_WRITE_WQBUFFER: { > unsigned long *ver_addr; > - dma_addr_t buf_handle; > int32_t my_empty_len, user_len, wqbuf_firstindex, wqbuf_lastindex; > uint8_t *pQbuffer, *ptmpuserbuffer; > + void *tmp; > > - ver_addr = pci_alloc_consistent(acb->pdev, 1032, &buf_handle); > - if (!ver_addr) { > + tmp = kmalloc(1032, GFP_KERNEL|GFP_DMA); > + ver_addr = (unsigned long *)tmp; Actually, just do ver_addr = kmalloc(...) instead > + if (!tmp) { > retvalue = ARCMSR_MESSAGE_FAIL; > goto message_out; > } > @@ -1482,7 +1492,7 @@ static int arcmsr_iop_message_xfer(struct AdapterControlBlock *acb, \ > retvalue = ARCMSR_MESSAGE_FAIL; > } > } > - pci_free_consistent(acb->pdev, 1032, ver_addr, buf_handle); > + kfree(tmp); > } > break; I can't work out why this was pci_alloc_consistent in the first place ... it's not used as consistent memory anywhere on the PCI bus James