public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: cmm@us.ibm.com, tytso@mit.edu, sandeen@redhat.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] vfs: tracepoints for buffer flag updates
Date: Thu, 12 Nov 2009 00:09:36 +0530	[thread overview]
Message-ID: <20091111183936.GA13999@skywalker.linux.vnet.ibm.com> (raw)
In-Reply-To: <1257964260-14020-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

This patchset when enabled with stacktrace will give output like the below

              dd-1905  [003]    26.445155: set_buffer_uptodate: bh = df5c28c0 device = vda block = 34817 new state= 0x23
              dd-1905  [003]    26.445156: <stack trace>
 => set_buffer_uptodate
 => __block_commit_write
 => block_write_end
 => ext3_writeback_write_end
 => generic_file_buffered_write
 => __generic_file_aio_write
 => generic_file_aio_write
 => do_sync_write
              dd-1905  [003]    26.445168: clear_buffer_new: bh = df5c28c0 device = vda block = 34817 new state = 0x23
              dd-1905  [003]    26.445169: <stack trace>
 => clear_buffer_new
 => __block_commit_write
 => block_write_end
 => ext3_writeback_write_end
 => generic_file_buffered_write
 => __generic_file_aio_write
 => generic_file_aio_write
 => do_sync_write
              dd-1905  [003]    26.445182: set_buffer_revokevalid: bh = df406540 device = vda block = 32835 new state= 0x310029
              dd-1905  [003]    26.445183: <stack trace>
 => journal_cancel_revoke
 => do_get_write_access
 => journal_get_write_access
 => __ext3_journal_get_write_access
 => ext3_reserve_inode_write
 => ext3_mark_inode_dirty
 => ext3_dirty_inode
 => __mark_inode_dirty
              dd-1905  [003]    26.445197: clear_buffer_revoked: bh = df406540 device = vda block = 32835 new state = 0x310029
              dd-1905  [003]    26.445198: <stack trace>
 => journal_cancel_revoke
 => do_get_write_access
 => journal_get_write_access
 => __ext3_journal_get_write_access
 => ext3_reserve_inode_write
 => ext3_mark_inode_dirty
 => ext3_dirty_inode
 => __mark_inode_dirty


-aneesh

      parent reply	other threads:[~2009-11-11 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 18:30 [RFC PATCH 1/2] vfs: tracepoints for buffer flag updates Aneesh Kumar K.V
2009-11-11 18:31 ` [RFC PATCH 2/2] ext[34]: Make sure we initialize the b_bdev field of dummy buffer_heads Aneesh Kumar K.V
2009-11-11 18:39 ` Aneesh Kumar K.V [this message]

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=20091111183936.GA13999@skywalker.linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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