Messages in this thread | | | From | Qian Cai <> | Subject | Re: [PATCH 1/3] iommu: match the original algorithm | Date | Wed, 27 Nov 2019 13:38:39 -0500 |
| |
> On Nov 27, 2019, at 1:01 PM, John Garry <john.garry@huawei.com> wrote: > > I haven't gone into the details, but this patch alone is giving this: > > root@(none)$ [ 123.857024] kmemleak: 8 new suspected memory leaks (see /sys/kernel/debug/kmemleak) > > root@(none)$ cat /sys/kernel/debug/kmemleak > unreferenced object 0xffff002339843000 (size 2048): > comm "swapper/0", pid 1, jiffies 4294898165 (age 122.688s) > hex dump (first 32 bytes): > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > backtrace: > [<000000001d2710bf>] kmem_cache_alloc+0x188/0x260 > [<00000000cc229a78>] init_iova_domain+0x1e8/0x2a8 > [<000000002646fc92>] iommu_setup_dma_ops+0x200/0x710 > [<00000000acc5fe46>] arch_setup_dma_ops+0x80/0x128 > [<00000000994e1e43>] acpi_dma_configure+0x11c/0x140 > [<00000000effe9374>] pci_dma_configure+0xe0/0x108 > [<00000000f614ae1e>] really_probe+0x210/0x548 > [<0000000087884b1b>] driver_probe_device+0x7c/0x148 > [<0000000010af2936>] device_driver_attach+0x94/0xa0 > [<00000000c92b2971>] __driver_attach+0xa4/0x110 > [<00000000c873500f>] bus_for_each_dev+0xe8/0x158 > [<00000000c7d0e008>] driver_attach+0x30/0x40 > [<000000003cf39ba8>] bus_add_driver+0x234/0x2f0 > [<0000000043830a45>] driver_register+0xbc/0x1d0 > [<00000000c8a41162>] __pci_register_driver+0xb0/0xc8 > [<00000000e562eeec>] sas_v3_pci_driver_init+0x20/0x28 > unreferenced object 0xffff002339844000 (size 2048): > comm "swapper/0", pid 1, jiffies 4294898165 (age 122.688s) > > [snip] > > And I don't feel like continuing until it's resolved....
Thanks for talking a hit by this before me. It is frustrating that people tend not to test their patches properly with things like kmemleak.
| |