From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: Error handling bug in fsys_rt_sigprocmask
Date: Wed, 19 May 2004 22:30:34 +0000 [thread overview]
Message-ID: <je7jv8yrqt.fsf@sykes.suse.de> (raw)
In-Reply-To: <jeekplxvah.fsf@sykes.suse.de>
David Mosberger <davidm@napali.hpl.hp.com> writes:
> There already is a check for a bad HOW value, but it comes too late.
> Your patch should be safe, but I'd like to fix it in a way that avoids
> the second (now unnecessary check). Let me see what I can come up with.
I did remove the second check. But there is now an additional bundle and
I couldn't find any way to avoid that.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-05-19 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 20:57 Error handling bug in fsys_rt_sigprocmask Andreas Schwab
2004-05-19 22:01 ` David Mosberger
2004-05-19 22:30 ` Andreas Schwab [this message]
2004-05-19 22:49 ` David Mosberger
2004-05-20 0:17 ` David Mosberger
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=je7jv8yrqt.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-ia64@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