linux-kernel - Re: [PATCH V2] x86:pci: Change sta2x11_dma_ops stucture to use switolb_dma_supported as it's dma

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150218180619.GA32158@gmail.com>
Date:	Wed, 18 Feb 2015 19:06:19 +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 V2] x86:pci: Change  sta2x11_dma_ops stucture to use
 switolb_dma_supported as it's dma_supported function in sta2x11-fixup.c


* Ingo Molnar <mingo@...nel.org> wrote:

> 
> * 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 this hardware. Otherwise this will cause a bug that will crash a operation
> > needing to access this function if an intended hardware operation needs to call
> > it but the kernel has the function pointer for this structure set to NULL
> > incorrectly.
> 
> Hm, I have asked a question for the v1 patch already:
> 
>   https://lkml.org/lkml/2015/2/16/30
> 
> is there an answer to my question?

Ok, found your reply meanwhile - somehow lkml didn't index 
the thread properly :-/

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/