linux-kernel - Re: [PATCH] arm: fix pci_set_consistent_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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100906083105X.fujita.tomonori@lab.ntt.co.jp>
Date:	Mon, 6 Sep 2010 08:32:45 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	linux@....linux.org.uk
Cc:	fujita.tomonori@....ntt.co.jp, khc@...waw.pl,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm: fix pci_set_consistent_dma_mask for dmabounce
	devices

On Sun, 5 Sep 2010 12:25:13 +0100
Russell King - ARM Linux <linux@....linux.org.uk> wrote:

> > This restores the trick that had worked.
> > 
> > btw, I can't compile ARCH_IXP4XX without the following patch:
> > 
> > http://www.spinics.net/lists/arm-kernel/msg95933.html
> > 
> > =
> > From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
> > Subject: [PATCH] arm: fix arm: fix pci_set_consistent_dma_mask for dmabounce devices
> > 
> > This fixes the regression caused by the commit
> > 6fee48cd330c68332f9712bc968d934a1a84a32a.
> > 
> > ARM needs to clip the dma coherent mask for dmabounce devices. This
> > restores the old trick.
> > 
> > Note that strictly speaking, the DMA API doesn't allow architectures
> > to do such but I'm not sure it's worth adding the new API to set the
> > dma mask that allows architectures to clip it.
> > 
> > Signed-off-by: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
> 
> Acked-by: Russell King <rmk+kernel@....linux.org.uk>

Should I send this to Linus? Or Can I assume that someone in ARM camp
will do?
--
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/