From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] I2C update for 2.6.10-rc1
Date: Mon, 8 Nov 2004 21:24:14 -0800 [thread overview]
Message-ID: <10999778542218@kroah.com> (raw)
In-Reply-To: <10999778541107@kroah.com>
ChangeSet 1.2014.1.2, 2004/10/22 12:52:13-07:00, ebs@ebshome.net
[PATCH] I2C: fix recently introduced race in IBM PPC4xx I2C driver
On Tue, Oct 19, 2004 at 10:21:08PM -0700, Eugene Surovegin wrote:
[snip]
> It looks like this change added race I tried to avoid here.
>
> This code is modeled after __wait_event_interruptible_timeout, where
> "prepare_to_wait" is done _before_ checking completion status. This
> change breaks this, e.g. if IRQ happens right after we check iic->sts,
> but before calling msleep_interruptible(). In this case we'll sleep
> much more than required (seconds instead of microseconds)
>
> Greg, if my analysis is correct, please rollback this change.
>
> Nishanth, I'd be nice if you CC'ed me with this patch, my e-mail is at
> the top of that source file.
Oh, well. I should have used wait_event_interruptible_timeout when I
ported this driver to 2.6.
This patch fixes recently introduced race and also cleans ups some
2.4-ism.
Signed-off-by: Eugene Surovegin <ebs@ebshome.net>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
drivers/i2c/busses/i2c-ibm_iic.c | 16 +++++-----------
1 files changed, 5 insertions(+), 11 deletions(-)
diff -Nru a/drivers/i2c/busses/i2c-ibm_iic.c b/drivers/i2c/busses/i2c-ibm_iic.c
--- a/drivers/i2c/busses/i2c-ibm_iic.c 2004-11-08 18:56:20 -08:00
+++ b/drivers/i2c/busses/i2c-ibm_iic.c 2004-11-08 18:56:20 -08:00
@@ -412,18 +412,12 @@
if (dev->irq >= 0){
/* Interrupt mode */
- wait_queue_t wait;
- init_waitqueue_entry(&wait, current);
-
- add_wait_queue(&dev->wq, &wait);
- if (in_8(&iic->sts) & STS_PT)
- msleep_interruptible(dev->adap.timeout * 1000);
- remove_wait_queue(&dev->wq, &wait);
-
- if (unlikely(signal_pending(current))){
+ ret = wait_event_interruptible_timeout(dev->wq,
+ !(in_8(&iic->sts) & STS_PT), dev->adap.timeout * HZ);
+
+ if (unlikely(ret < 0))
DBG("%d: wait interrupted\n", dev->idx);
- ret = -ERESTARTSYS;
- } else if (unlikely(in_8(&iic->sts) & STS_PT)){
+ else if (unlikely(in_8(&iic->sts) & STS_PT)){
DBG("%d: wait timeout\n", dev->idx);
ret = -ETIMEDOUT;
}
next prev parent reply other threads:[~2004-11-09 5:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 5:22 [BK PATCH] I2C update for 2.6.10-rc1 Greg KH
2004-11-09 5:24 ` [PATCH] " Greg KH
2004-11-09 5:24 ` Greg KH [this message]
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 10:17 ` Jean Delvare
2004-11-09 11:12 ` Arjan van de Ven
2004-11-09 14:10 ` Jean Delvare
2004-11-09 9:29 ` [BK PATCH] " Jean Delvare
2004-11-09 15:21 ` Greg KH
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=10999778542218@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.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