From: Ben Myers <bpm@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: trace xfs_name strings correctly
Date: Mon, 26 Mar 2012 13:37:36 -0500 [thread overview]
Message-ID: <20120326183736.GW7762@sgi.com> (raw)
In-Reply-To: <20120228110140.GA20760@infradead.org>
On Tue, Feb 28, 2012 at 06:01:40AM -0500, Christoph Hellwig wrote:
> Strings store in an xfs_name structure are often not NUL terminated,
> print them using the correct printf specifiers that make use of the
> string length store in the xfs_name structure.
>
> Reported-by: Brian Candler <B.Candler@pobox.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks good.
Reviewed-by: Ben Myers <bpm@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-03-26 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 11:01 [PATCH] xfs: trace xfs_name strings correctly Christoph Hellwig
2012-03-26 18:37 ` Ben Myers [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=20120326183736.GW7762@sgi.com \
--to=bpm@sgi.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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