public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sstewartgallus00 at mylangara dot bc.ca" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17204] New: race condition in nice
Date: Sun, 27 Jul 2014 04:39:00 -0000 [thread overview]
Message-ID: <bug-17204-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17204
Bug ID: 17204
Summary: race condition in nice
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: sstewartgallus00 at mylangara dot bc.ca
CC: drepper.fsp at gmail dot com
nice is implemented as calling getpriority and than setting the priority as
higher and than calling getpriority again but this is racy as other tasks can
call setpriority concurrently. This bug probably doesn't actually cause any
problems but it could still be fixed. Fixing this bug would also reduce the
amount of system calls by one which would be nice. Glibc should not call
getpriority to get the new value of the priority after.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-07-27 4:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 4:39 sstewartgallus00 at mylangara dot bc.ca [this message]
2014-07-27 7:13 ` [Bug libc/17204] " schwab@linux-m68k.org
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=bug-17204-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).