From: Wolfram Sang <wsa@kernel.org>
To: Chen Zhongjin <chenzhongjin@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
jdelvare@suse.com
Subject: Re: [PATCH v2] i2c: piix4: Fix adapter not be removed in piix4_remove()
Date: Tue, 1 Nov 2022 13:29:22 +0100 [thread overview]
Message-ID: <Y2ERIsY9/IKLuXoG@shikoro> (raw)
In-Reply-To: <20221027121353.181695-1-chenzhongjin@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2017 bytes --]
On Thu, Oct 27, 2022 at 08:13:53PM +0800, Chen Zhongjin wrote:
> In piix4_probe(), the piix4 adapter will be registered in:
>
> piix4_probe()
> piix4_add_adapters_sb800() / piix4_add_adapter()
> i2c_add_adapter()
>
> Based on the probed device type, piix4_add_adapters_sb800() or single
> piix4_add_adapter() will be called.
> For the former case, piix4_adapter_count is set as the number of adapters,
> while for antoher case it is not set and kept default *zero*.
>
> When piix4 is removed, piix4_remove() removes the adapters added in
> piix4_probe(), basing on the piix4_adapter_count value.
> Because the count is zero for the single adapter case, the adapter won't
> be removed and makes the sources allocated for adapter leaked, such as
> the i2c client and device.
>
> These sources can still be accessed by i2c or bus and cause problems.
> An easily reproduced case is that if a new adapter is registered, i2c
> will get the leaked adapter and try to call smbus_algorithm, which was
> already freed:
>
> Triggered by: rmmod i2c_piix4 && modprobe max31730
>
> BUG: unable to handle page fault for address: ffffffffc053d860
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> Oops: 0000 [#1] PREEMPT SMP KASAN
> CPU: 0 PID: 3752 Comm: modprobe Tainted: G
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
> RIP: 0010:i2c_default_probe (drivers/i2c/i2c-core-base.c:2259) i2c_core
> RSP: 0018:ffff888107477710 EFLAGS: 00000246
> ...
> <TASK>
> i2c_detect (drivers/i2c/i2c-core-base.c:2302) i2c_core
> __process_new_driver (drivers/i2c/i2c-core-base.c:1336) i2c_core
> bus_for_each_dev (drivers/base/bus.c:301)
> i2c_for_each_dev (drivers/i2c/i2c-core-base.c:1823) i2c_core
> i2c_register_driver (drivers/i2c/i2c-core-base.c:1861) i2c_core
> do_one_initcall (init/main.c:1296)
> do_init_module (kernel/module/main.c:2455)
> ...
> </TASK>
Applied to for-current, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-11-01 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 12:13 [PATCH v2] i2c: piix4: Fix adapter not be removed in piix4_remove() Chen Zhongjin
2022-10-27 14:12 ` Jean Delvare
2022-11-01 12:29 ` Wolfram Sang [this message]
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=Y2ERIsY9/IKLuXoG@shikoro \
--to=wsa@kernel.org \
--cc=chenzhongjin@huawei.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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