From: Steve Dickson <SteveD@redhat.com>
To: NFS@lists.sourceforge.net
Subject: Re: [PATCH] spinlock recursion on inode number mismatches
Date: Fri, 18 Nov 2005 06:42:51 -0500 [thread overview]
Message-ID: <437DBE3B.7030304@RedHat.com> (raw)
In-Reply-To: <1132270232.8017.2.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> Hmm... That will cause us to call make_bad_inode on all errors in
> nfs_update_inode().
Good point... I didn't see that...
>
> How about something like the appended patch instead?
Yes... creating away for nfs_zap_caches() to be called
while holding the inode spinlock does in deed fix the
problem... nice work... thanks!
steved.
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-11-18 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 22:07 [PATCH] spinlock recursion on inode number mismatches Steve Dickson
2005-11-17 23:30 ` Trond Myklebust
2005-11-18 11:42 ` Steve Dickson [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-17 22:34 Lever, Charles
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=437DBE3B.7030304@RedHat.com \
--to=steved@redhat.com \
--cc=NFS@lists.sourceforge.net \
/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.