linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: linux-cifs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/3] cifs: tighten up cifs_iget matching criteria
Date: Mon, 28 Jun 2010 07:10:10 -0400	[thread overview]
Message-ID: <1277723413-23769-1-git-send-email-jlayton@redhat.com> (raw)

These patches are intended to help reduce the number of false matches
that cifs_iget does. They simply try to make the code do some extra
checking of the cached inodes against the new file's attributes when a
uniqueid matches one that's already in cache.

I've tested these against samba and windows. They seem to work and help
reduce the false positives that can cause server inode numbers to be
disabled.

This patchset is intended for 2.6.36. The patches are in the cifs-2.6.36
branch of my kernel.org tree:

http://git.kernel.org/?p=linux/kernel/git/jlayton/linux.git;a=shortlog;h=refs/heads/cifs-2.6.36

Jeff Layton (3):
  cifs: don't allow cifs_iget to match inodes of the wrong type
  cifs: use CreationTime like an i_generation field
  cifs: reduce false positives with inode aliasing serverino
    autodisable

 fs/cifs/cifsfs.c   |    2 +
 fs/cifs/cifsglob.h |    2 +
 fs/cifs/inode.c    |   54 ++++++++++++++++++++++++++++++++++++++++-----------
 fs/cifs/readdir.c  |    1 +
 4 files changed, 47 insertions(+), 12 deletions(-)


             reply	other threads:[~2010-06-28 11:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 11:10 Jeff Layton [this message]
2010-06-28 11:10 ` [PATCH 1/3] cifs: don't allow cifs_iget to match inodes of the wrong type Jeff Layton
     [not found] ` <1277723413-23769-1-git-send-email-jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-06-28 11:10   ` [PATCH 2/3] cifs: use CreationTime like an i_generation field Jeff Layton
     [not found]     ` <1277723413-23769-3-git-send-email-jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-06-28 13:26       ` Suresh Jayaraman
2010-06-28 13:47         ` Jeff Layton
2010-11-22 19:55     ` Jeff Layton
     [not found]       ` <AANLkTimtg0vFVQ5HGo+nq7rE=Z4Sob=z7LuVCMFgWdnv@mail.gmail.com>
     [not found]         ` <AANLkTimtg0vFVQ5HGo+nq7rE=Z4Sob=z7LuVCMFgWdnv-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-11-22 20:31           ` Jeff Layton
     [not found]             ` <20101122153125.68ee4ee6-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2010-11-22 20:59               ` Jeremy Allison
2010-12-07  1:55                 ` Jeff Layton
2010-06-28 11:10   ` [PATCH 3/3] cifs: reduce false positives with inode aliasing serverino autodisable 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=1277723413-23769-1-git-send-email-jlayton@redhat.com \
    --to=jlayton@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).