The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "\"Dieter Müller (BOI GmbH)\"" <dieter.mueller@boi.at>
To: linux-kernel@vger.kernel.org
Subject: blocking file lock functions (lockf,flock,fcntl) do not return after timer signal
Date: Wed, 12 Oct 2005 09:54:44 +0200	[thread overview]
Message-ID: <434CC144.6000504@boi.at> (raw)

bug description:

flock, lockf, fcntl do not return even after the signal SIGALRM  has 
been raised and the signal handler function has been executed
the functions should return with a return value EWOULDBLOCK as described 
in the man pages


test:

sequence of called functions (start the test in 2 terminal sessions)
1. signal
2. setitimer
3. fopen
4. fileno
5. fcntl with F_WRLCK and F_SETLKW (or flock or lockf)
6. getchar (to keep the lock in the 1st session; now start the 2nd)
in the 2nd session the file lock function (fcntl) will not return


kernel versions:

2.4.18-64GB-SMP
2.4.21psetlvm
2.6.11.4-21.9-default


please reply or CC to mailto:boi@boi.at



Dieter Mueller-Wipperfuerth
BOI GmbH.
Spazgasse 4
4040 Linz
Austria


             reply	other threads:[~2005-10-12  7:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-12  7:54 "Dieter Müller (BOI GmbH)" [this message]
2005-10-12 12:48 ` blocking file lock functions (lockf,flock,fcntl) do not return after timer signal Alex Riesen
2005-10-12 13:09   ` linux-os (Dick Johnson)
2005-10-12 14:39   ` Trond Myklebust
2005-10-12 15:10     ` Alex Riesen
2005-10-12 15:20       ` linux-os (Dick Johnson)
2005-10-12 15:37         ` Michael Kerrisk
2005-10-12 15:43           ` linux-os (Dick Johnson)
2005-10-12 16:05             ` Michael Kerrisk
2005-10-12 16:06             ` Mark Lord
2005-10-12 21:15         ` Alex Riesen
2005-10-12 16:36       ` Trond Myklebust

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=434CC144.6000504@boi.at \
    --to=dieter.mueller@boi.at \
    --cc=boi@boi.at \
    --cc=linux-kernel@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