From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Jiri Slaby" <jirislaby@gmail.com>
Cc: "Simon Arlott" <simon@fire.lp0.eu>,
"Matthias Kaehlcke" <matthias.kaehlcke@gmail.com>,
"Arjan van de Ven" <arjan@infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: [PATCH] fix unchecked mutex_lock_interruptible (was Re: use mutex instead of semaphore in RocketPort driver)
Date: Wed, 23 May 2007 18:25:49 +0530 [thread overview]
Message-ID: <a781481a0705230555j6fcf46eav43cc95f6d1a7ae6f@mail.gmail.com> (raw)
On 5/23/07, Jiri Slaby <jirislaby@gmail.com> wrote:
> Simon Arlott napsal(a):
> > On 22/05/07 21:06, Matthias Kaehlcke wrote:
> >> would the following resolve the problem?
> >>
> >> if(mutex_lock_interruptible(&info->write_mtx)) return
> >> -ERESTARTSYS
> >>
> >> thanks for your comments
Hum. I remember suggesting the fix when this came few weeks back,
somehow the older version seems to have made it into Linus' tree.
> > No. At least one user of tty_operations/tty_driver's write function
> > doesn't check the return value so it would never be retried, mutex_lock
> > should be used instead.
Replacing mutex_lock_interruptible() with a mutex_lock() could be a
change in behaviour visible to userspace. Best to continue to use
_interruptible. Returning EINTR would be safe choice because if
Simon's right that this isn't retried, we could end up breaking
userspace that isn't quite ready to see ERESTARTSYS coming out of
a write(2), but ...
> Who? There are some drivers that returns ERESTARTSYS from write function.
Right, several others in drivers/char/ do return ERESTARTSYS. Hope
somebody picks this up -- no email listed in MAINTAINERS for this.
---
Check the return of mutex_lock_interruptible() in drivers/char/rocket.c
and return ERESTARTSYS if we were interrupted.
Signed-off-by: Satyam Sharma <satyam.sharma@gmail.com>
---
drivers/char/rocket.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
---
diff -ruNp a/drivers/char/rocket.c b/drivers/char/rocket.c
--- a/drivers/char/rocket.c 2007-05-20 04:11:54.000000000 +0530
+++ b/drivers/char/rocket.c 2007-05-23 18:14:35.000000000 +0530
@@ -1702,7 +1702,8 @@ static int rp_write(struct tty_struct *t
if (count <= 0 || rocket_paranoia_check(info, "rp_write"))
return 0;
- mutex_lock_interruptible(&info->write_mtx);
+ if (mutex_lock_interruptible(&info->write_mtx))
+ return -ERESTARTSYS;
#ifdef ROCKET_DEBUG_WRITE
printk(KERN_INFO "rp_write %d chars...", count);
next reply other threads:[~2007-05-23 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 12:55 Satyam Sharma [this message]
2007-05-23 13:59 ` Matthias Kaehlcke
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=a781481a0705230555j6fcf46eav43cc95f6d1a7ae6f@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.kaehlcke@gmail.com \
--cc=simon@fire.lp0.eu \
/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
all inboxes | Powered by JetHome®