Bug 10814 - utmp locking uses alarm() which can't fully restore timer
Summary: utmp locking uses alarm() which can't fully restore timer
Status: RESOLVED WONTFIX
Alias: None
Product: glibc
Classification: Unclassified
Component: libc (show other bugs)
Version: 2.9
: P2 normal
Target Milestone: ---
Assignee: Ulrich Drepper
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-20 10:08 UTC by didier
Modified: 2019-08-05 15:30 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description didier 2009-10-20 10:08:13 UTC 
Hi,

A timer set with a non null it_interval via setitimer() is corrupted after a
call to utmp functions.

Maybe LOCK_FILE could use setitimer() rather than alarm() ?
Comment 1 Ulrich Drepper 2009-10-20 11:30:18 UTC 
This is how it always worked and it does indeed work.  Some programs might
depend or expect this horrible implementation.  These interfaces are badly
designed due to the historic bagage and you have to know how and when to use them.