Re: [bug report] kmemleak from driver i2c_piix4

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

 



On Fri, Jun 17, 2022 at 3:48 PM Jean Delvare <jdelvare@xxxxxxx> wrote:
>
> Hi Yi Zhang,
>
> On Sat, 11 Jun 2022 17:08:20 +0800, Yi Zhang wrote:
> > I found this kmemleak from dmesg, pls help check it, thanks.
> >
> > unreferenced object 0xffff8882be7fa500 (size 64):
> >   comm "systemd-udevd", pid 851, jiffies 4294724190 (age 1880.031s)
> >   hex dump (first 32 bytes):
> >     00 03 d8 fe 00 00 00 00 07 03 d8 fe 00 00 00 00  ................
> >     20 95 85 c0 ff ff ff ff 00 02 40 80 00 00 00 00   .........@.....
> >   backtrace:
> >     [<00000000ee7a7c0d>] __request_region+0x4f/0xc0
> >     [<000000000a0d9a20>] piix4_sb800_region_request+0x69/0x150 [i2c_piix4]
> >     [<00000000bbbc5f63>] piix4_setup_sb800.constprop.0+0xfd/0x4a0 [i2c_piix4]
> >     [<0000000060da9710>] piix4_probe+0x111/0x780 [i2c_piix4]
> >     [<0000000061a2fccd>] local_pci_probe+0xdf/0x170
> >     [<00000000f879d262>] pci_call_probe+0x15f/0x4b0
> >     [<00000000b1b4235f>] pci_device_probe+0xee/0x230
> >     [<000000007b0612f3>] really_probe+0x3d7/0xa10
> >     [<0000000016a94cde>] __driver_probe_device+0x2ab/0x460
> >     [<00000000fc08f31f>] driver_probe_device+0x49/0x120
> >     [<00000000c7600ea6>] __driver_attach+0x1c1/0x420
> >     [<00000000d075fad5>] bus_for_each_dev+0x121/0x1a0
> >     [<000000003a0c2b72>] bus_add_driver+0x39f/0x570
> >     [<00000000389c6619>] driver_register+0x20f/0x390
> >     [<00000000e1871c0e>] do_one_initcall+0xfc/0x560
> >     [<00000000899e6968>] do_init_module+0x190/0x620
>
> Thanks for reporting.
>
> Which kernel version are you running? Are there patches applied to the
> i2c-piix4 driver?
The latest linux tree

>
> Which line of the source code does
> piix4_sb800_region_request+0x69/0x150 resolve to?

(gdb) l *(piix4_sb800_region_request+0x69)
0x2b9 is in piix4_sb800_region_request (drivers/i2c/busses/i2c-piix4.c:185).
180 {
181 if (mmio_cfg->use_mmio) {
182 struct resource *res;
183 void __iomem *addr;
184
185 res = request_mem_region_muxed(SB800_PIIX4_FCH_PM_ADDR,
186        SB800_PIIX4_FCH_PM_SIZE,
187        "sb800_piix4_smb");
188 if (!res) {
189 dev_err(dev,

>
> Which PCI device does the driver bind to? "lspci -nn | grep" SMBus
> should tell.
# lspci -nn | grep SMBus
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus
Controller [1022:790b] (rev 61)
>
> Which messages are printed to the kernel log when you load and unload
> the i2c-piix4 driver?

[ 1400.379156] piix4_smbus 0000:00:14.0: SMBus Host Controller at
0xb00, revision 0
[ 1400.379164] piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus
port selection
[ 1400.381759] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host
Controller at 0xb20

>
> --
> Jean Delvare
> SUSE L3 Support
>


-- 
Best Regards,
  Yi Zhang




[Index of Archives]     [Linux GPIO]     [Linux SPI]     [Linux Hardward Monitoring]     [LM Sensors]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux