[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: EDEADLK in svn_repos_fs_begin_txn_for_commit2

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Thu, 27 Jan 2011 16:40:02 +0000

Blair Zajac <blair_at_orcaware.com> writes:

> On 1/27/11 1:35 AM, Philip Martin wrote:
>> Philip Martin<philip.martin_at_wandisco.com> writes:
>>> It appears that the kernel deadlock detection sometimes produces false
>>> positives
>> I believe I was mistaken when I assumed that fcntl() would block just
>> the thread making the call; rereading the man page I think it is the
>> whole process that blocks. That means this is not a false positive.
> I believe your first inclination was correct, that fcntl() just blocks
> the calling thread. How could one system call block other threads
> from doing work?

I'm not sure. The kernel knows which threads are part of the process so
it could block them all.

> I'm guessing the kernel doesn't look if the process is multithreaded
> and if its making progress, it just assumes it is single threaded,
> which is why it has to return EDEADLK.

A little experimenting on my Linux box shows that when one thread of
svnserve is blocked in fcntl() during a commit other threads still
respond. So this probably does count as a false positive deadlock.

Received on 2011-01-27 17:40:45 CET

This is an archived mail posted to the Subversion Dev mailing list.