From: Jeff Layton <jlayton@redhat.com>
To: linux-cifs-client@lists.samba.org
Cc: linux-fsdevel@vger.kernel.org, sjayaraman@suse.de
Subject: [PATCH 0/2] cifs: fix "Busy inodes after umount" issues (try #2)
Date: Mon, 24 May 2010 09:55:50 -0400 [thread overview]
Message-ID: <1274709352-13599-1-git-send-email-jlayton@redhat.com> (raw)
This is the second attempt at a patchset to fix a recent outbreak of
"Busy inodes after umount" issues with cifs. The approach is basically
the same.
The first patch in the original set has also been dropped since Al
pointed out that the existing behavior is more clear. The second and
third patches have also been merged since they touch the same areas of
code. Finally a few bugs in the original set have been fixed as well.
With this set, I've not been able to reproduce any "busy inodes after
umount" issues, but it would be nice to have some extra eyeballs and
testing on this set before it goes in.
Jeff Layton (2):
cifs: move cifs_new_fileinfo call out of cifs_posix_open
cifs: pass instantiated filp back after open call
fs/cifs/cifsproto.h | 1 -
fs/cifs/dir.c | 76 +++++++++++++++++++++++++++++---------------------
fs/cifs/file.c | 59 +++++++++-------------------------------
3 files changed, 57 insertions(+), 79 deletions(-)
next reply other threads:[~2010-05-24 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 13:55 Jeff Layton [this message]
2010-05-24 13:55 ` [PATCH 1/2] cifs: move cifs_new_fileinfo call out of cifs_posix_open Jeff Layton
2010-05-24 13:55 ` [PATCH 2/2] cifs: pass instantiated filp back after open call Jeff Layton
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=1274709352-13599-1-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sjayaraman@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).