linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [bug report] kmemleak from driver i2c_piix4
Date: Fri, 17 Jun 2022 09:38:18 +0200	[thread overview]
Message-ID: <20220617093818.37a721a3@endymion.delvare> (raw)
In-Reply-To: <CAHj4cs_NnJLYwhxPvDGnu4QFwS_XbgeJ7b2jOcDvBM3F+w7z0w@mail.gmail.com>

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?

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

Which PCI device does the driver bind to? "lspci -nn | grep" SMBus
should tell.

Which messages are printed to the kernel log when you load and unload
the i2c-piix4 driver?

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2022-06-17  7:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  9:08 [bug report] kmemleak from driver i2c_piix4 Yi Zhang
2022-06-17  7:38 ` Jean Delvare [this message]
2022-06-17 13:33   ` Yi Zhang
2022-06-21 12:48     ` Jean Delvare
2022-06-21 14:29       ` Terry Bowman
2022-06-22  5:16         ` Yi Zhang
2022-06-22  6:39         ` Jean Delvare
2022-06-22 13:41           ` Terry Bowman
2022-06-22 15:36           ` Terry Bowman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220617093818.37a721a3@endymion.delvare \
    --to=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=yi.zhang@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).