From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Teigland <teigland@redhat.com>
Date: Tue, 13 May 2008 15:13:30 -0500
Subject: [Cluster-devel] Cluster Project branch, STABLE2,
	updated. cluster-2.03.02-7-ga6b6a30
In-Reply-To: <1210708873.3513.1.camel@localhost.localdomain>
References: <20080513190854.7210.qmail@sourceware.org>
	<1210708873.3513.1.camel@localhost.localdomain>
Message-ID: <20080513201330.GA27026@redhat.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On Tue, May 13, 2008 at 09:01:13PM +0100, Steven Whitehouse wrote:
> Hi,
> 
> It might be a silly question, but this looks to me like trying to fix a
> kernel bug by adding a userland one. Why not simply update the kernel to
> return the correct value?

Yes, there's already a kernel fix in dlm.git, see
  "dlm: fix plock dev_write return value"

http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/teigland/dlm.git;a=shortlog;h=next

Suppressing the message spamming is a good solution in the mean time, and
has a better chance of getting to customers before the kernel patch.