LKML Archive on
help / color / mirror / Atom feed
From: "Aaron Wiebe" <>
Subject: uninterruptable fcntl calls
Date: Fri, 2 Feb 2007 13:54:31 -0500	[thread overview]
Message-ID: <> (raw)


I've run into a situation where fcntl F_SETLKW calls lock up nearly
completely.  I've tried several approaches to handle this case, and
have yet to come up with some method of handling this.  I've never
really ventured outside userspace, so I'm turning to this list to try
and get a handle on this.

Over NFSv3 udp, this situation takes place VERY rarely, however with
the volume I do, its creating a problem.

In short, I am attempting to read or write lock, and the call hangs to
the point where a sigkill is not captured - no signal is.  I've tried
alarming out and I've tried switching the socket to nonblocking -
nothing I can think of prevents or even allows me to handle the case.
I understand NFS locking can be rather sketchy at times - but all I
need is the ability to handle the case.

I can force the process to die by sending a sigkill, then stracing.
The strace reports the process as sigstop, then processes the kill

All I need here is a method of capturing this case.  I can "repair"
the stuck lock by regenerating the file, but I can't capture the case
in order to handle this in code.

Any help would be useful - I am currently running compiled
with the NFS patches from, but this case was happening
before applying those patches.  I'd be happy to provide any more
information nessecary.  I've been struggling with this one for a few
months now.



rt_sigaction(SIGALRM, {0xb7f56640, [ALRM], 0}, {SIG_DFL}, 8) = 0
alarm(120)                              = 0
fcntl64(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}


fcntl64(3, F_GETFL)                     = 0x8002 (flags O_RDWR|O_LARGEFILE)
fcntl64(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}

Code used for locking:

static int db_lock(int fd, int type)
    struct flock fl;
    struct timespec *tv = (struct timespec *) malloc(sizeof(struct timespec));
    int ret, c = 0;

    if(!(fd > 0))
        return -1;

    /* after two minutes, wig out */

    fl.l_whence = SEEK_SET;
    fl.l_start = 0;
    fl.l_len = 0;
    fl.l_type = type;


    while((ret = fcntl(fd, F_SETLKW, &fl)) < 0)
        if(c > 600)
            /* we've been waiting for 60 seconds... */
            my_error("stuck on fcntl request, aborting");
            return -1;
        tv->tv_nsec = 100;   /* 10th of a second wait */
        tv->tv_sec = 0;
        nanosleep(tv, NULL);
    return ret;

             reply	other threads:[~2007-02-02 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 18:54 Aaron Wiebe [this message]
2007-02-02 19:28 ` Fwd: uninterruptable fcntl calls Aaron Wiebe
2007-02-02 19:45   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 NNTP newsgroup(s).