public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* Trailing garbage in event tracing output
@ 2012-02-02 11:52 Brian Candler
  2012-02-02 14:09 ` Christoph Hellwig
  0 siblings, 1 reply; 2+ messages in thread
From: Brian Candler @ 2012-02-02 11:52 UTC (permalink / raw)
  To: xfs

Just a minor issue, but when I did some XFS tracing using the instructions
at http://lwn.net/Articles/341899/ I found that there was trailing garbage
in the filenames logged in xfs_lookup.  Example:

...
        bonnie++-26179 [000] 322388.834204: xfs_iunlock: dev 8:32 ino 0xfe1e6 flags ILOCK_SHARED caller xfs_free_eofblocks
        bonnie++-26179 [000] 322388.834212: xfs_lookup: dev 8:32 dp ino 0xfb50d name 000000295aSl688>v??*N
        bonnie++-26179 [000] 322388.834213: xfs_ilock: dev 8:32 ino 0xfb50d flags ILOCK_SHARED caller xfs_ilock_map_shared
...

(where I think the real filename was "000000295aSl688"). I would guess the
logger is expecting null-terminated strings but they aren't.

This is with the stock kernel from Ubuntu 11.10 server x86_64:
Linux storage1 3.0.0-15-server #26-Ubuntu SMP Fri Jan 20 19:07:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Regards,

Brian.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-02-02 14:09 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-02 11:52 Trailing garbage in event tracing output Brian Candler
2012-02-02 14:09 ` Christoph Hellwig

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox