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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <971fbb889da38ca4e60f3dedde29ea43e9338d68.camel@xry111.site>
Date: Fri, 20 Sep 2024 05:41:51 +0800
From: Xi Ruoyao <xry111@...111.site>
To: Christoph Hellwig <hch@...radead.org>, Linus Torvalds
	 <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, iommu@...ts.linux.dev
Subject: Re: [GIT PULL] dma-mapping updates for Linux 6.12

On Thu, 2024-09-19 at 09:54 +0200, Christoph Hellwig wrote:
> The following changes since commit 47ac09b91befbb6a235ab620c32af719f8208399:
> 
>   Linux 6.11-rc4 (2024-08-18 13:17:27 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.12-2024-09-19
> 
> for you to fetch changes up to a5fb217f13f74b2af2ab366ffad522bae717f93c:
> 
>   dma-mapping: reflow dma_supported (2024-09-12 16:28:00 +0200)
> 
> ----------------------------------------------------------------
> dma-mapping updates for linux 6.12
> 
>  - support DMA zones for arm64 systems where memory starts at > 4GB
>    (Baruch Siach, Catalin Marinas)
>  - support direct calls into dma-iommu and thus obsolete dma_map_ops for
>    many common configurations (Leon Romanovsky)
>  - add DMA-API tracing (Sean Anderson)
>  - remove the not very useful return value from various dma_set_* APIs
>    (Christoph Hellwig)
>  - misc cleanups and minor optimizations (Chen Y, Yosry Ahmed,
>    Christoph Hellwig)

Hi Christoph and Linus,

This breaks using my laptop camera with gstreamer (with "gst-launch-1.0
v4l2src ! videoconvert ! autovideosink" or GNOME snapshot).

"git bisect" gives:

The first bad commit could be any of:
b5a73bf4d1de95e620bf5f592557b81f71c76f0e
833bd284a45448f04ab9fcd4fdf7ef594d458eed
c42a01264ba1497eb3193c08ff3c2656d98250a6
560a861ab4174b42240157ab5cebe36b8c7bc418
b5c58b2fdc427e7958412ecb2de2804a1f7c1572
334304ac2baca7f3e821c47cf5129d90e7a6b1e6

(I had to use "git bisect skip" several times because I encountered
kernel panic on boot at some revisions.)

Reverting the merge fixes the issue.  I'm not sure if this is related to
the camera model (I can borrow another camera to test tomorrow).

-- 
Xi Ruoyao <xry111@...111.site>
School of Aerospace Science and Technology, Xidian University

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ