cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 2/2] gfs2_edit: Include dirent.de_rahead in directory listings
Date: Thu, 10 Sep 2015 12:07:12 +0100	[thread overview]
Message-ID: <55F16460.5030302@redhat.com> (raw)
In-Reply-To: <55F05E01.3030205@redhat.com>

On 09/09/15 17:27, Andrew Price wrote:
> On 09/09/15 16:55, Andreas Gruenbacher wrote:
>> When dumping a directory, for directory each entry, also print how
>> many blocks
>> of metadata can be read ahead when reading in the inode the entry
>> points at.
>>
>> Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
>> ---
>>   gfs2/edit/extended.c | 5 +++--
>>   1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/gfs2/edit/extended.c b/gfs2/edit/extended.c
>> index e5cb12c..7a219ee 100644
>> --- a/gfs2/edit/extended.c
>> +++ b/gfs2/edit/extended.c
>> @@ -342,13 +342,14 @@ static int display_leaf(struct iinfo *ind)
>>                       strcpy(edit_fmt, "%llx");
>>                   }
>>               }
>> -            print_gfs2("%d/%d [%08x] %lld/%lld (0x%llx/0x%llx): ",
>> +            print_gfs2("%d/%d [%08x] %lld/%lld (0x%llx/0x%llx) +%d: ",
>>                      total_dirents, d + 1,
>>                      ind->ii[0].dirent[d].dirent.de_hash,
>>                      ind->ii[0].dirent[d].dirent.de_inum.no_formal_ino,
>>                      ind->ii[0].dirent[d].block,
>>                      ind->ii[0].dirent[d].dirent.de_inum.no_formal_ino,
>> -                   ind->ii[0].dirent[d].block);
>> +                   ind->ii[0].dirent[d].block,
>> +                   (unsigned int)ind->ii[0].dirent[d].dirent.de_rahead);
>
> It would be better to use %u for an unsigned int. We don't have
> __attribute__((format(printf...))) on print_gfs2 yet but it would catch
> that.

I've pushed both patches, including the above tweak, and added another 
patch to support older versions which don't have the de_rahead field (< 
Linux 3.15).

Thanks,
Andy



  reply	other threads:[~2015-09-10 11:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 15:55 [Cluster-devel] [PATCH 1/2] libgfs2: Add support for dirent.de_rahead Andreas Gruenbacher
2015-09-09 15:55 ` [Cluster-devel] [PATCH 2/2] gfs2_edit: Include dirent.de_rahead in directory listings Andreas Gruenbacher
2015-09-09 16:27   ` Andrew Price
2015-09-10 11:07     ` Andrew Price [this message]
2015-09-10 12:51       ` Andreas Grünbacher
2015-09-10 22:04     ` Andreas Gruenbacher
2015-09-10 22:05       ` [Cluster-devel] [PATCH 1/2] gfs2: Fix printf format errors on x86 Andreas Gruenbacher
2015-09-10 22:05         ` [Cluster-devel] [PATCH 2/2] gfs2_edit: Add attribute printf for print_gfs2 Andreas Gruenbacher
2015-09-11 10:45           ` Andrew Price
2015-09-11 10:45       ` [Cluster-devel] [PATCH 2/2] gfs2_edit: Include dirent.de_rahead in directory listings Andrew Price
2015-09-11 11:02         ` Andreas Gruenbacher
2015-09-11 11:28           ` [Cluster-devel] gfs2 on-disk headers in user space Andrew Price
2015-09-11 11:40             ` Andreas Grünbacher
2015-09-11 11:57               ` Andrew Price

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=55F16460.5030302@redhat.com \
    --to=anprice@redhat.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;
as well as URLs for NNTP newsgroup(s).