CEPH filesystem development
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@gnu.org>
To: "Yan, Zheng" <zheng.z.yan@intel.com>
Cc: ceph-devel@vger.kernel.org, sage@inktank.com
Subject: Re: [PATCH] mds: update backtrace when old format inode is touched
Date: Fri, 23 Aug 2013 08:36:00 -0300	[thread overview]
Message-ID: <orli3sk5b3.fsf@livre.home> (raw)
In-Reply-To: <ortxigk9c2.fsf@livre.home> (Alexandre Oliva's message of "Fri, 23 Aug 2013 07:09:01 -0300")

On Aug 23, 2013, Alexandre Oliva <oliva@gnu.org> wrote:

> On Aug 22, 2013, "Yan, Zheng" <zheng.z.yan@intel.com> wrote:
>> We updated inode format version to 7 when introducing inode backtrace.
>> If we found a inode's format version < 7 when fetching the inode, set
>> the inode's backtrace_version to 0, to indicate the inode's backtrace
>> is out of data. When touching a inode with backtrace_version == 0, we
>> also update its backtrace.

>> +  if (pi->backtrace_version == 0)
>> +    pi->update_backtrace();
   
> AFAICT all this does is to update the backtrace version number in the
> cached-in-memory inode.  What am I missing?  Or is the code missing
> something? :-)

N/m, I see now that this eventually causes _mark_dirty_parent to be
called, which in turn gets the parent attribute updated.
inode_t::is_backtrace_updated() means exactly the opposite of what I
expected ;-)

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer

  reply	other threads:[~2013-08-23 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23  1:42 [PATCH] mds: update backtrace when old format inode is touched Yan, Zheng
2013-08-23 10:09 ` Alexandre Oliva
2013-08-23 11:36   ` Alexandre Oliva [this message]
2013-10-16 23:35 ` Gregory Farnum
2013-10-21  1:14   ` Yan, Zheng

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=orli3sk5b3.fsf@livre.home \
    --to=oliva@gnu.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@inktank.com \
    --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