From: David Sterba <dsterba@suse.cz>
To: Zach Brown <zab@redhat.com>
Cc: Wang Shilong <wangshilong1991@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V2 1/2] Btrfs-progs: make pretty_sizes() work less error prone
Date: Wed, 10 Jul 2013 14:49:16 +0200 [thread overview]
Message-ID: <20130710124916.GK18204@suse.cz> (raw)
In-Reply-To: <20130709202443.GJ18717@lenny.home.zabbo.net>
On Tue, Jul 09, 2013 at 01:24:43PM -0700, Zach Brown wrote:
> > The original codes don't handle error gracefully and some places
> > forget to free memory. We can allocate memory before calling pretty_sizes(),
> > for example, we can use static memory allocation and we don't have to deal
> > with memory allocation fails.
>
> I agree that callers shouldn't have to know to free allocated memory.
>
> But I think that we can do better and not have callers need to worry
> about per-call string storage at all.
>
> How about something like this?
Neat trick! A few neat-picks below. Besides, I guess we can use this
sort of trick with the fi-df patches.
> --- a/utils.c
> +++ b/utils.c
> @@ -1153,12 +1153,13 @@ out:
>
> static char *size_strs[] = { "", "KB", "MB", "GB", "TB",
> "PB", "EB", "ZB", "YB"};
I'll drop the ZB, YB suffixes.
> --- a/utils.h
> +++ b/utils.h
> @@ -44,7 +44,15 @@ int check_mounted_where(int fd, const char *file, char *where, int size,
> struct btrfs_fs_devices **fs_devices_mnt);
> int btrfs_device_already_in_root(struct btrfs_root *root, int fd,
> int super_offset);
> -char *pretty_sizes(u64 size);
> +
> +void pretty_size_snprintf(u64 size, char *str, size_t str_bytes);
> +#define pretty_sizes(size) \
and rename it to pretty_size as it takes only one number
> + ({ \
> + static __thread char _str[16]; \
16 is not enough for exabyte scale, that needs at least 20 bytes + 1 for 0.
len(str(2**64)) = 20
-> 24
> + pretty_size_snprintf(size, _str, sizeof(_str)); \
pretty_size_snprintf((size), _str, sizeof(_str)); \
As these are only trivial changes I'll fix them at commit time.
> + _str; \
> + })
> +
> int get_mountpt(char *dev, char *mntpt, size_t size);
> int btrfs_scan_block_devices(int run_ioctl);
> u64 parse_size(char *s);
> --
> 1.7.11.7
>
next prev parent reply other threads:[~2013-07-10 12:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 9:58 [PATCH V2 1/2] Btrfs-progs: make pretty_sizes() work less error prone Wang Shilong
2013-07-09 20:24 ` Zach Brown
2013-07-09 23:05 ` Wang Shilong
2013-07-10 12:49 ` David Sterba [this message]
2013-07-10 15:59 ` Zach Brown
2013-07-10 14:30 ` [PATCH] btrfs-progs: per-thread, per-call pretty buffer David Sterba
2013-07-10 15:31 ` Wang Shilong
2013-07-10 15:51 ` David Sterba
2013-07-10 16:16 ` Hugo Mills
2013-07-10 17:39 ` David Sterba
2013-07-10 17:40 ` [PATCH] btrfs-progs: use IEC units for sizes David Sterba
2014-09-04 11:43 ` [PATCH] btrfs-progs: per-thread, per-call pretty buffer Anand Jain
2014-09-04 19:45 ` Zach Brown
2014-09-05 7:11 ` Anand Jain
2014-09-05 15:55 ` Zach Brown
2014-09-05 16:20 ` David Sterba
2014-09-15 12:27 ` David Sterba
2015-02-27 17:53 ` David Sterba
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=20130710124916.GK18204@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangshilong1991@gmail.com \
--cc=zab@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).