[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Atomic file locking update

From: Svante Signell
Subject: Re: Atomic file locking update
Date: Thu, 27 Nov 2014 13:49:53 +0100

On Thu, 2014-11-27 at 13:20 +0100, Samuel Thibault wrote:
> Justus Winter, le Thu 27 Nov 2014 12:51:56 +0100, a écrit :
> > Just to be sure I understand the change correctly, the downgrade is
> > somewhat trivial, right?
> Yes, we just have to notify potential writers.
> > Because your patch has an explicit 'tell
> > others we are upgrading' and my symmetry-sense is tingling.
> Yes, upgrading is hard and we want to avoid new readers keeping blocking
> it.

As discussed on #debian-hurd IRC, these changes are conflicting with the
record file locking patches. When you upgrade Hurd again, I need to
rebase these patches another time. Maybe we should keep your patches and
forget about record file locking?

As written on IRC the record lock patched hurd/glibc does not play well
with tdbtorture. On the other hand, I've been running at least 5 VMs
with these patches since August without problems. Of course these
patches ar not up to GCS standards, so let's forget about the whole
issue. I continue to rebase and apply them privately for every hurd/libc
release to come.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]