From: Thomas Schlichter <schlicht@uni-mannheim.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: patch for errno-issue (with soundcore)
Date: Mon, 13 Jan 2003 15:57:33 +0100 [thread overview]
Message-ID: <200301131557.33135.schlicht@uni-mannheim.de> (raw)
In-Reply-To: <1042470839.18624.19.camel@irongate.swansea.linux.org.uk>
On Mon, 13. Jan. 2003 16:13, Alan Cox wrote:
> This actually shows a bug that has always been lurking. What if we load two
> modules firmware at the same time. errno needs to be task private or we
> perhaps need an errno_sem ?
OK, I think I see the problem now!
But is soundcore the only place where 'errno' is used? Does this problem not
occur if any task modifies the errno value and an other one depends on its
previous value? I think this could happen even if no modules are used...
next prev parent reply other threads:[~2003-01-13 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 13:57 patch for errno-issue (with soundcore) Thomas Schlichter
2003-01-13 14:04 ` Bob_Tracy(0000)
2003-01-13 15:13 ` Alan Cox
2003-01-13 14:57 ` Thomas Schlichter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-13 16:33 Petr Vandrovec
2003-01-13 17:10 ` Thomas Schlichter
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=200301131557.33135.schlicht@uni-mannheim.de \
--to=schlicht@uni-mannheim.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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