From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>, linux-i2c@vger.kernel.org
Cc: lkml <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>, Andi Shyti <andi.shyti@kernel.org>,
Mario Limonciello <mario.limonciello@amd.com>,
narasimhan.v@amd.com
Subject: Re: i2c-designware: NULL ptr at RIP: 0010:regmap_read+0x12/0x70
Date: Tue, 2 Jan 2024 15:42:30 +0200 [thread overview]
Message-ID: <8169d773-f9ec-4092-b036-9e4fd59966c3@linux.intel.com> (raw)
In-Reply-To: <20231229120820.GCZY62tM7z4v2XmOAZ@fat_crate.local>
Hi
On 12/29/23 14:08, Borislav Petkov wrote:
> Looking at the call stack, I see
>
> 2409205acd3c ("i2c: designware: fix __i2c_dw_disable() in case master is holding SCL low")
>
> which does that dev->map deref in __i2c_dw_disable() but maybe ->map is
> invalid by then...?
>
> Just a stab in the dark anyway...
>
Do you run same tests on vanilla? I.e. do you see this on v6.7-rc8?
I'm curious to know is this already existing issue or regression because
of recent cleanup patches in linux-next between v6.7-rc8..
drivers/i2c/busses/i2c-designware-*.
next prev parent reply other threads:[~2024-01-02 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 12:08 i2c-designware: NULL ptr at RIP: 0010:regmap_read+0x12/0x70 Borislav Petkov
2024-01-02 13:42 ` Jarkko Nikula [this message]
[not found] ` <DM4PR12MB508654DF49FE079D6C283D658961A@DM4PR12MB5086.namprd12.prod.outlook.com>
2024-01-03 15:25 ` Jarkko Nikula
[not found] ` <DM4PR12MB5086DE2882C7C5044697B1C38967A@DM4PR12MB5086.namprd12.prod.outlook.com>
2024-01-04 13:40 ` Jarkko Nikula
2024-01-06 16:06 ` Andy Shevchenko
[not found] ` <DM4PR12MB508652E9A422CF639C2FEEC0896A2@DM4PR12MB5086.namprd12.prod.outlook.com>
2024-01-09 10:11 ` Jarkko Nikula
2024-01-10 22:56 ` Kim Phillips
2024-01-11 13:01 ` Jarkko Nikula
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=8169d773-f9ec-4092-b036-9e4fd59966c3@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@linux.intel.com \
--cc=narasimhan.v@amd.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