public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Jean Delvare <jdelvare@suse.de>, Linux I2C <linux-i2c@vger.kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH] i2c: i801: Don't generate an interrupt on bus reset
Date: Wed, 26 May 2021 12:10:37 +0300	[thread overview]
Message-ID: <0d540f23-14a7-4812-d94b-bd344879b3d9@linux.intel.com> (raw)
In-Reply-To: <20210525170336.213a19b4@endymion>

Hi

On 5/25/21 6:03 PM, Jean Delvare wrote:
> Now that the i2c-i801 driver supports interrupts, setting the KILL bit
> in a attempt to recover from a timed out transaction triggers an
> interrupt. Unfortunately, the interrupt handler (i801_isr) is not
> prepared for this situation and will try to process the interrupt as
> if it was signaling the end of a successful transaction. In the case
> of a block transaction, this can result in an out-of-range memory
> access.
> 
> This condition was reproduced several times by syzbot:
> https://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e
> https://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e
> https://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e
> https://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb
> https://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a
> https://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79
> 
> So disable interrupts while trying to reset the bus. Interrupts will
> be enabled again for the following transaction.
> 
> Fixes: 636752bcb517 ("i2c-i801: Enable IRQ for SMBus transactions")
> Reported-by: syzbot+b4d3fd1dfd53e90afd79@syzkaller.appspotmail.com
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> ---
>   drivers/i2c/busses/i2c-i801.c |    6 ++----
>   1 file changed, 2 insertions(+), 4 deletions(-)
> 
I hope I managed to test this properly. At least I was able to trigger 
KASAN quite easily and after your patch not anymore.

My test was to run "i2cdump -y 0 0x50 i" a few times with this hack:

--- a/drivers/i2c/busses/i2c-i801.c
+++ b/drivers/i2c/busses/i2c-i801.c
@@ -653,6 +653,7 @@ static irqreturn_t i801_isr(int irq, void *dev_id)
  	struct i801_priv *priv = dev_id;
  	u16 pcists;
  	u8 status;
+	static int count = 0;

  	/* Confirm this is our interrupt */
  	pci_read_config_word(priv->pci_dev, SMBPCISTS, &pcists);
@@ -676,8 +677,10 @@ static irqreturn_t i801_isr(int irq, void *dev_id)
  	status &= SMBHSTSTS_INTR | STATUS_ERROR_FLAGS;
  	if (status) {
  		outb_p(status, SMBHSTSTS(priv));
-		priv->status = status;
-		wake_up(&priv->waitq);
+		if ((count++ % 10)) {
+				priv->status = status;
+				wake_up(&priv->waitq);
+		}
  	}

  	return IRQ_HANDLED;

Tested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>

  reply	other threads:[~2021-05-26  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 15:03 [PATCH] i2c: i801: Don't generate an interrupt on bus reset Jean Delvare
2021-05-26  9:10 ` Jarkko Nikula [this message]
2021-05-27 19:56 ` 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=0d540f23-14a7-4812-d94b-bd344879b3d9@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hkallweit1@gmail.com \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@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