public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug libc/10840] glibc could now fix broken F_GETOWN [not found] <bug-10840-131@http.sourceware.org/bugzilla/> @ 2014-07-01 5:35 ` fweimer at redhat dot com 0 siblings, 0 replies; 4+ messages in thread From: fweimer at redhat dot com @ 2014-07-01 5:35 UTC (permalink / raw) To: glibc-bugs https://sourceware.org/bugzilla/show_bug.cgi?id=10840 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |security- -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libc/10840] New: glibc could now fix broken F_GETOWN @ 2009-10-24 3:46 mtk dot manpages at gmail dot com 2009-10-29 17:14 ` [Bug libc/10840] " drepper at redhat dot com ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: mtk dot manpages at gmail dot com @ 2009-10-24 3:46 UTC (permalink / raw) To: glibc-bugs Userspace has long lived with a limitation in the system call convention employed on Linux/x86 and some other architectures that means that if a file descriptor is owned by a process group ID less than 4096, then, instead of returning that ID as a negative function result from fcntl() F_GETOWN, glibc misinterprets it as a system call error. This is because glibc (has little choice but to) interpret negative system call returns in the range -1 to -4095 as indicating an error. This limitation means that an application that uses process groups to receive "I/O possible" signals can't reliably use F_GETOWN to discover which process group owns a file descriptor. Starting with kernel 2.6.32, Linux adds F_GETOWN_EX, which provides a way of returning the owner of a file descriptor via a structure (f_owner_ex), which AFAICS means that glibc could since Linux 2.6.32 intercept F_GETOWN operations and use F_GETOWN_EX to ensure that the right value is returned to userspace. -- Summary: glibc could now fix broken F_GETOWN Product: glibc Version: 2.10 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: mtk dot manpages at gmail dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=10840 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libc/10840] glibc could now fix broken F_GETOWN 2009-10-24 3:46 [Bug libc/10840] New: " mtk dot manpages at gmail dot com @ 2009-10-29 17:14 ` drepper at redhat dot com 2009-10-29 17:15 ` schwab at linux-m68k dot org 2009-10-31 9:08 ` mtk dot manpages at gmail dot com 2 siblings, 0 replies; 4+ messages in thread From: drepper at redhat dot com @ 2009-10-29 17:14 UTC (permalink / raw) To: glibc-bugs ------- Additional Comments From drepper at redhat dot com 2009-10-29 17:14 ------- Fixed in git. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED http://sourceware.org/bugzilla/show_bug.cgi?id=10840 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libc/10840] glibc could now fix broken F_GETOWN 2009-10-24 3:46 [Bug libc/10840] New: " mtk dot manpages at gmail dot com 2009-10-29 17:14 ` [Bug libc/10840] " drepper at redhat dot com @ 2009-10-29 17:15 ` schwab at linux-m68k dot org 2009-10-31 9:08 ` mtk dot manpages at gmail dot com 2 siblings, 0 replies; 4+ messages in thread From: schwab at linux-m68k dot org @ 2009-10-29 17:15 UTC (permalink / raw) To: glibc-bugs ------- Additional Comments From schwab at linux-m68k dot org 2009-10-29 17:15 ------- Note that F_[SG]ETOWN_EX are not usable yet because their values clash with F_[GS]ETLK64. -- http://sourceware.org/bugzilla/show_bug.cgi?id=10840 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libc/10840] glibc could now fix broken F_GETOWN 2009-10-24 3:46 [Bug libc/10840] New: " mtk dot manpages at gmail dot com 2009-10-29 17:14 ` [Bug libc/10840] " drepper at redhat dot com 2009-10-29 17:15 ` schwab at linux-m68k dot org @ 2009-10-31 9:08 ` mtk dot manpages at gmail dot com 2 siblings, 0 replies; 4+ messages in thread From: mtk dot manpages at gmail dot com @ 2009-10-31 9:08 UTC (permalink / raw) To: glibc-bugs ------- Additional Comments From mtk dot manpages at gmail dot com 2009-10-31 09:08 ------- Thanks! -- http://sourceware.org/bugzilla/show_bug.cgi?id=10840 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-07-01 5:35 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <bug-10840-131@http.sourceware.org/bugzilla/> 2014-07-01 5:35 ` [Bug libc/10840] glibc could now fix broken F_GETOWN fweimer at redhat dot com 2009-10-24 3:46 [Bug libc/10840] New: " mtk dot manpages at gmail dot com 2009-10-29 17:14 ` [Bug libc/10840] " drepper at redhat dot com 2009-10-29 17:15 ` schwab at linux-m68k dot org 2009-10-31 9:08 ` mtk dot manpages at gmail dot com
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).