[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3e0/0x4d0)



On Wednesday, 1 February 2023 02:52:13 CET Dr. David Alan Gilbert wrote:
> bisected:
> GOOD [37fcacb50be7071d146144a6c5c5bf0194b9a1cf] phy: PHY_FSL_LYNX_28G should
> depend on ARCH_LAYERSCAPE BAD [f5ff79fddf0efecca538046b5cc20fb3ded2ec4f]
> dma-mapping: remove CONFIG_DMA_REMAP GOOD
> [e62c17f0455a74b182ce6373e2777817256afaa1] MAINTAINERS: update maintainer
> list of DMA MAPPING BENCHMARK GOOD
> [0fb3436b4b36cf69f4544385aa2bb8c5a4913509] sparc: Remove usage of the
> deprecated "pci-dma-compat.h" API GOOD
> [fba09099c6e506608e05e08ac717bf34501f821b] media: v4l2-pci-skeleton: Remove
> usage of the deprecated "pci-dma-compat.h" API
> 
> dg@major:~/kernel/kernel-clone$ git bisect good
> f5ff79fddf0efecca538046b5cc20fb3ded2ec4f is the first bad commit
> commit f5ff79fddf0efecca538046b5cc20fb3ded2ec4f
> Author: Christoph Hellwig <hch@lst.de>
> Date:   Sat Feb 26 16:40:21 2022 +0100
> 
>     dma-mapping: remove CONFIG_DMA_REMAP
> 
> That sounds like a believable cause given that it's IOMMU related
> and device related.

Thanks for that thorough analyses!
If you're 'penguin42' on IRC, then I'd suggest to present your findings to
iommu@lists.linux.dev as both the author and the reviewer are highly likely 
subscribed to that list.

scripts/get_maintainer.pl drivers/iommu/dma-iommu.c
scripts/get_maintainer.pl kernel/dma/Makefile

list them both and both results have also that ML in their result.

HTH

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: