[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20150310044500.GA9015@gmail.com>
Date: Tue, 10 Mar 2015 05:45:01 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Nicholas Krause <xerofoify@...il.com>
Cc: bhelgaas@...gle.com, tglx@...utronix.de, mingo@...hat.com,
hpa@...or.com, x86@...nel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND] x86:pci: Change sta2x11_dma_ops stucture to use
switolb_dma_supported as it's dma_supported function in sta2x11-fixup.c
* Nicholas Krause <xerofoify@...il.com> wrote:
> This changes the structure sta2x11_dma_ops stucture to use switolb_dma_supported as it's
> function for dma_supported hardware verus setting this value to NULL as this should be set
> correctly for when dma_supported function needs to be called for hardware needing this
> function to be supported. Otherwise hardware needing this function to be supported will
> either cause a kernel panic or oops due to a NULL pointer being dereferenced in the
> structure, sta1x11_dma_ops for the dma_supported function. Further more in order to
> prevent a kernel panic or oops here due to a NULL pointer being deferred here we add the
> function, swiotlb_dma_supported as the dma_supported function for the structure,
> sta2x11_dma_ops.
Pleasedontresendtotallyunstructuredandunreadablechangelogs.
You also (still) don't explain where and how this supposed crash might
happen in practice. Please don't resend unless you've addressed those
deficiencies.
I.e. I'm not convinced you know what you are modifying there and what
effects your modifications will have.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists