From: David Sterba <dsterba@suse.cz>
To: Anand Jain <Anand.Jain@oracle.com>
Cc: David Sterba <dsterba@suse.cz>,
linux-btrfs@vger.kernel.org, Zach Brown <zab@zabbo.net>
Subject: Re: [PATCH] btrfs-progs: use less memory for pretty_size_mode buffers
Date: Mon, 9 Mar 2015 11:38:22 +0100 [thread overview]
Message-ID: <20150309103822.GA5841@twin.jikos.cz> (raw)
In-Reply-To: <54F9FE3A.4030405@oracle.com>
On Fri, Mar 06, 2015 at 02:21:30PM -0500, Anand Jain wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x00000800007caf18 in __vsnprintf_chk () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install
> glibc-2.12-1.132.0.8.el6.sparc64 libblkid-2.17.2-12.14.0.2.el6.sparc64
> libuuid-2.17.2-12.14.0.2.el6.sparc64 lzo-2.03-3.1.el6.1.sparc64
> zlib-1.2.3-29.el6.sparc64
Thanks for testing. Is it the same error as before? IOW if the patch
hellped to reduce the stack usage or if it's a bug in the patch itself.
prev parent reply other threads:[~2015-03-09 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 18:37 [PATCH] btrfs-progs: use less memory for pretty_size_mode buffers David Sterba
2015-03-06 19:21 ` Anand Jain
2015-03-09 10:38 ` David Sterba [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=20150309103822.GA5841@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=Anand.Jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zab@zabbo.net \
/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).