public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Yan, Zheng" <zheng.z.yan@intel.com>
Cc: linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org,
	sage@inktank.com, viro@zeniv.linux.org.uk
Subject: Re: [PATCH 2/2] fs: fix dentry_lru_prune()
Date: Fri, 8 Mar 2013 13:04:45 +1100	[thread overview]
Message-ID: <20130308020445.GB23616@dastard> (raw)
In-Reply-To: <1362656256-4397-1-git-send-email-zheng.z.yan@intel.com>

On Thu, Mar 07, 2013 at 07:37:36PM +0800, Yan, Zheng wrote:
> From: "Yan, Zheng" <zheng.z.yan@intel.com>
> 
> dentry_lru_prune() should always call file system's d_prune callback.

Why? What bug does this fix?

Cheers,

Dave.

-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2013-03-08  2:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 11:37 [PATCH 2/2] fs: fix dentry_lru_prune() Yan, Zheng
2013-03-08  2:04 ` Dave Chinner [this message]
2013-03-08  2:43   ` Yan, Zheng
2013-03-08  6:27     ` Dave Chinner
2013-03-08  6:40       ` Yan, Zheng
2013-03-09  9:35         ` Dave Chinner

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=20130308020445.GB23616@dastard \
    --to=david@fromorbit.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sage@inktank.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=zheng.z.yan@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox