mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.17: sys_sigsuspend does not return value
Date: Sat, 19 Jan 2002 00:59:04 +0100	[thread overview]
Message-ID: <jewuyfw6rb.fsf@sykes.suse.de> (raw)
In-Reply-To: <20020118210825.GA6175@elf.ucw.cz>
In-Reply-To: <20020118210825.GA6175@elf.ucw.cz> (Pavel Machek's message of "Fri, 18 Jan 2002 22:08:26 +0100")

Pavel Machek <pavel@suse.cz> writes:

|> Hi!
|> 
|> >From 2.4.17:
|> 
|> asmlinkage int
|> sys_sigsuspend(int history0, int history1, old_sigset_t mask)
|> {
|>         struct pt_regs * regs = (struct pt_regs *) &history0;
|>         sigset_t saveset;
|> 
|>         mask &= _BLOCKABLE;
|>         spin_lock_irq(&current->sigmask_lock);
|>         saveset = current->blocked;
|>         siginitset(&current->blocked, mask);
|>         recalc_sigpending(current);
|>         spin_unlock_irq(&current->sigmask_lock);
|> 
|>         regs->eax = -EINTR;
|>         while (1) {
           ^^^^^^^^^
|>                 current->state = TASK_INTERRUPTIBLE;
|>                 schedule();
|>                 if (do_signal(regs, &saveset))
|>                         return -EINTR;
|>         }
|> }
|> 
|> ...Which looks to me like it returns something undefined when
|> do_signal returns 0.

There is only one return path from this function.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

      reply	other threads:[~2002-01-18 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-18 21:08 Pavel Machek
2002-01-18 23:59 ` Andreas Schwab [this message]

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=jewuyfw6rb.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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®