All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Wendy Cheng <s.wendy.cheng@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
	nfs@lists.sourceforge.net, linux-nfs@vger.kernel.org,
	Lon Hohberger <lhh@redhat.com>
Subject: Re: [PATCH] lockd: unlock lockd locks held for a certain filesystem
Date: Wed, 23 Apr 2008 17:39:19 -0400	[thread overview]
Message-ID: <20080423213918.GH8302@fieldses.org> (raw)
In-Reply-To: <480FA769.40900@gmail.com>

On Wed, Apr 23, 2008 at 05:17:29PM -0400, Wendy Cheng wrote:
> J. Bruce Fields wrote:
>> On Wed, Apr 23, 2008 at 04:39:11PM -0400, Wendy Cheng wrote:
>>   
>>> #if defined(BRUCE_CHECK_THIS_OUT)
>>> error = nlmsvc_failover_path(nd.path.mnt->mnt_sb);
>>> #else
>>> error = nlmsvc_failover_path(nd.mnt->mnt_sb);
>>> #endif
>>>     
>>
>> The vfsmount and dentry got moved into the path argument sometime in the
>> last kernel version or so.  Is there a macro defining the latter as a
>> shortcut for the former?  I didn't see one.
>>
>>
>>   
> Sorry, just realized my kernel is too old (2.6.25)

2.6.25 is'nt that old quite yet!  OK, I get the idea, anyway.

> .. It would be  
> cumbersome for me to test RHCS with newer kernels. Linux is really a  
> moving target :( ....
>
> Anyway, will think of something else to test this out..

OK, thanks.  I did some very basic tests, and I'm not terribly worried
about it; at worst, it's unlikely to break anything that's already
working.  But let me know what you find out.

I've sent off my merge request for 2.6.26, but I may try to bundle this
up with a few smaller patches I think I've missed and submit another
request before the weekend.

--b.

  reply	other threads:[~2008-04-23 21:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16  9:17 [NFS] Forcefully resetting a lock Erik Hensema / HostingXS Internet Services
     [not found] ` <200804161117.24734.hensema-yolSOB3tinz/D1n+0JDH9g@public.gmane.org>
2008-04-16 11:44   ` Jeff Layton
2008-04-16 15:15   ` Wendy Cheng
2008-04-16 18:42     ` J. Bruce Fields
2008-04-16 19:39       ` Wendy Cheng
2008-04-17 21:52         ` J. Bruce Fields
2008-04-18 14:02           ` Wendy Cheng
2008-04-18 18:19             ` J. Bruce Fields
2008-04-22 23:15               ` J. Bruce Fields
2008-04-22 23:17                 ` [NFS] [PATCH] lockd: unlock lockd locks associated with a given server ip J. Bruce Fields
2008-04-22 23:18                   ` [NFS] [PATCH] lockd: unlock lockd locks held for a certain filesystem J. Bruce Fields
2008-04-23  2:57                     ` Wendy Cheng
2008-04-23  7:44                     ` Christoph Hellwig
2008-04-23 17:12                       ` J. Bruce Fields
2008-04-23 17:52                         ` Christoph Hellwig
2008-04-23 20:01                           ` J. Bruce Fields
2008-04-23 20:39                         ` Wendy Cheng
2008-04-23 21:02                           ` J. Bruce Fields
2008-04-23 21:17                             ` Wendy Cheng
2008-04-23 21:39                               ` J. Bruce Fields [this message]
2008-04-23 21:44                                 ` Wendy Cheng

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=20080423213918.GH8302@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=hch@lst.de \
    --cc=lhh@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=s.wendy.cheng@gmail.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.