linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Nick Dokos <nicholas.dokos@hp.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
	Justin Maggard <jmaggard10@gmail.com>,
	Andreas Dilger <adilger@sun.com>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] Fix counting routines in blknum.c to take/return __u32 counts.
Date: Sun, 6 Sep 2009 12:37:04 -0400	[thread overview]
Message-ID: <20090906163704.GK3055@mit.edu> (raw)
In-Reply-To: <13135.1251925342@alphaville.usa.hp.com>

On Wed, Sep 02, 2009 at 05:02:22PM -0400, Nick Dokos wrote:
> From e8c790ab8a0f06b4c89a5b6ddba2a36f033c742c Mon Sep 17 00:00:00 2001
> From: Nick Dokos <nicholas.dokos@hp.com>
> Date: Wed, 2 Sep 2009 16:52:09 -0400
> Subject: [PATCH] Fix counting routines in blknum.c to take/return __u32 counts.
> 
> Several routines in lib/ext2fs/blknum.c:
> 
>         ext2fs_bg_free_blocks_count()
>         ext2fs_bg_free_inodes_count()
>         ext2fs_bg_used_dirs_count()
>         ext2fs_bg_itable_unused()
> 
> and their _set() counterparts, operate as if they are dealing with
> blk64_t quantities, but they should be dealing with __u32 counts
> instead.
> 
> Signed-off-by: Nick Dokos <nicholas.dokos@hp.com>

Added to the e2fsprogs pu branch / 64-bit patch set.

BTW, note that this patch by itself caused the regression test suite
to explode spectactularly, since there was a number of printf-style
format statements that had to be changed so that dumpe2fs, debugfs
et. al, would work correctly after changing the above-mentioned
routines to return 32-bit values instead of 64-bit values.

I've fixed this before adding it to the e2fsprogs patch set.

Even though we do need to add more 64-bit tests, I do appreciate it if
people could test their patches using "make check" before sending
patches them to the ext4 list.

	    	   	  	 	    - Ted

  parent reply	other threads:[~2009-09-06 16:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 21:43 [PATCH] libext2fs: use ext2fs_blocks_count() in ext2fs_open2() Eric Sandeen
2009-09-02  5:59 ` Andreas Dilger
2009-09-02  6:05   ` Justin Maggard
2009-09-02 16:43     ` Eric Sandeen
2009-09-02 21:02       ` Nick Dokos
2009-09-02 21:28         ` Justin Maggard
2009-09-02 21:31           ` Eric Sandeen
2009-09-02 21:37           ` Nick Dokos
2009-09-02 21:43             ` Eric Sandeen
2009-09-02 21:45               ` Justin Maggard
2009-09-02 22:33                 ` Eric Sandeen
2009-09-02 22:55                   ` Andreas Dilger
2009-09-03  2:41                     ` Eric Sandeen
2009-09-02 22:28         ` Theodore Tso
2009-09-02 23:12           ` Nick Dokos
2009-09-06 16:37         ` Theodore Tso [this message]
2009-09-06 17:41           ` [PATCH] Fix counting routines in blknum.c to take/return __u32 counts Nick Dokos
2009-09-06 18:19             ` Theodore Tso
2009-09-06 16:30 ` [PATCH] libext2fs: use ext2fs_blocks_count() in ext2fs_open2() Theodore Tso

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=20090906163704.GK3055@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger@sun.com \
    --cc=jmaggard10@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=nicholas.dokos@hp.com \
    --cc=sandeen@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).