From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org
Cc: Baruch Siach <baruch@tkos.co.il>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: smbus: fix NULL function pointer dereference
Date: Fri, 26 Apr 2024 10:28:40 +0300 [thread overview]
Message-ID: <e46f56f4-f28f-4fb6-4249-554059f9fc2f@gmail.com> (raw)
In-Reply-To: <20240426064408.7372-1-wsa+renesas@sang-engineering.com>
On 4/26/24 9:44 AM, Wolfram Sang wrote:
> Brauch reported an OOPS when using the designware controller as target
He's Baruch... :-)
> only. Target-only modes break the assumption of one transfer function
> always being available. Fix this by always checking the pointer in
> __i2c_transfer.
>
> Reported-by: Baruch Siach <baruch@tkos.co.il>
> Closes: https://lore.kernel.org/r/4269631780e5ba789cf1ae391eec1b959def7d99.1712761976.git.baruch@tkos.co.il
> Fixes: 4b1acc43331d ("i2c: core changes for slave support")
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[...]
MBR, Sergey
next prev parent reply other threads:[~2024-04-26 7:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 6:44 [PATCH] i2c: smbus: fix NULL function pointer dereference Wolfram Sang
2024-04-26 7:28 ` Sergei Shtylyov [this message]
2024-04-26 8:39 ` Wolfram Sang
2024-04-26 8:32 ` Baruch Siach
2024-04-26 9:52 ` Wolfram Sang
2024-05-30 13:24 ` Jean Delvare
2024-06-04 8:50 ` Wolfram Sang
2024-06-04 15:11 ` Jean Delvare
2024-06-04 20:08 ` Wolfram Sang
2024-06-05 9:20 ` Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2024-04-10 15:12 Baruch Siach
2024-04-26 6:43 ` Wolfram Sang
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=e46f56f4-f28f-4fb6-4249-554059f9fc2f@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=baruch@tkos.co.il \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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