All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: Jeff Layton <jlayton@redhat.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	linux-nfs@vger.kernel.org
Subject: Re: list corruption in locks_start_grace with 2.6.28-rc3
Date: Mon, 24 Nov 2008 10:26:11 -0500	[thread overview]
Message-ID: <x49wsetdu24.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <49289B2D.1090404@opengridcomputing.com> (Tom Tucker's message of "Sat, 22 Nov 2008 17:52:13 -0600")

Tom Tucker <tom@opengridcomputing.com> writes:

> Jeff M/L:
>
> Could you guys confirm that this patch fixes the problem? I was able
> to reproduce Jeff Layton's problem and this patch resolved
> the under-reference condition for me.

With this patch and the one that Bruce posted, I no longer see any
problems.  Bruce, you can add a Tested-by: Jeff Moyer
<jmoyer@redhat.com> to your patch submission.

Thanks, guys!

Cheers,
Jeff

  parent reply	other threads:[~2008-11-24 15:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 16:15 list corruption in locks_start_grace with 2.6.28-rc3 Jeff Moyer
     [not found] ` <x498wrokjj8.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2008-11-20 20:37   ` J. Bruce Fields
2008-11-21 15:28     ` Jeff Moyer
     [not found]       ` <x49ej15gktp.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2008-11-22  0:54         ` J. Bruce Fields
2008-11-22 14:22           ` Jeff Layton
     [not found]             ` <20081122092237.1ab81cdb-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2008-11-22 20:48               ` Tom Tucker
2008-11-22 23:52                 ` Tom Tucker
2008-11-23  1:00                   ` Jeff Layton
2008-11-24 15:26                   ` Jeff Moyer [this message]
     [not found]                     ` <x49wsetdu24.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2008-11-24 16:16                       ` J. Bruce Fields

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=x49wsetdu24.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tom@opengridcomputing.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.