From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: rtc-linux@googlegroups.com
Cc: jikos@jikos.cz, Peter Zijlstra <a.p.zijlstra@chello.nl>,
Gabriel C <nix.or.die@googlemail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [rtc-linux] Re: BUG: lock held when returning to user space
Date: Mon, 29 Oct 2007 13:20:20 +0100 [thread overview]
Message-ID: <20071029132020.4731aa01@i1501.lan.towertech.it> (raw)
In-Reply-To: <Pine.LNX.4.64.0710280043590.18815@twin.jikos.cz>
On Sun, 28 Oct 2007 00:47:15 +0200 (CEST)
Jiri Kosina <jikos@jikos.cz> wrote:
> Yes, but the fact is that is really is invalid use of mutex -- because the
> mutex owner could become seriously wrong after fork() or sending the
> filedescriptor through unix socket ... this easily leads to broken
> situation.
>
> This seems to have been introduced in e824290e5d ... Alessandro, could you
> convert this to test_and_set_bit()/clear_bit() semantics instead of a
> mutex please?
Hi Jiri,
I was away for the weekend and just saw the whole discussion
and your patch and I'm happy to ack it. Thank you very much
a thanks to Gabriel for the bug report!
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2007-10-29 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 14:19 BUG: lock held when returning to user space Gabriel C
2007-10-27 15:12 ` Jiri Kosina
2007-10-27 15:28 ` Peter Zijlstra
2007-10-27 15:46 ` Andrew Morton
2007-10-28 11:12 ` Jiri Kosina
2007-10-29 12:20 ` Alessandro Zummo
2007-10-27 16:35 ` Linus Torvalds
2007-10-27 22:47 ` Jiri Kosina
2007-10-29 12:20 ` Alessandro Zummo [this message]
2007-10-27 15:47 ` Arjan van de Ven
2007-10-27 16:09 ` Peter Zijlstra
2007-10-27 17:05 ` Arjan van de Ven
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=20071029132020.4731aa01@i1501.lan.towertech.it \
--to=alessandro.zummo@towertech.it \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nix.or.die@googlemail.com \
--cc=rtc-linux@googlegroups.com \
--cc=torvalds@linux-foundation.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