From: Mark Tinguely <tinguely@sgi.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/8] xfsprogs: misc small fixes
Date: Wed, 20 Feb 2013 16:09:58 -0600 [thread overview]
Message-ID: <512549B6.70705@sgi.com> (raw)
In-Reply-To: <1359240032-11576-1-git-send-email-sandeen@redhat.com>
On 01/26/13 16:40, Eric Sandeen wrote:
> A handful of fixes from looking over a Coverity scan.
>
> The strncpy fixes (1/8, 5/8) might not be too critical,
> but I think they can't hurt.
>
> The libxfs xfs_alloc_arg initialization (2/8) might clash with Dave's
> libxfs syncup, it can be dropped if it makes things difficult.
> Fixes a real bug though.
>
> Tested by a quick run through xfstests -g auto
>
> Thanks,
> -Eric
>
> [PATCH 1/8] libhandle: Guard against string overflow in path_to_fspath()
> [PATCH 2/8] libxfs: initialize xfs_alloc_arg structures
> [PATCH 3/8] libxfs: fix setup_cursor array allocation
> [PATCH 4/8] xfs_repair: Fix free of uninit ptr in xfs_acl_valid() error path
> [PATCH 5/8] xfs_fsr: guard against path string overflows
> [PATCH 6/8] xfs_fsr: check strdup results properly in initallfs()
> [PATCH 7/8] xfs_fsr: fix attribute no_change_count logic
> [PATCH 8/8] xfs_fsr: remove extraneous close() in fsrallfs()
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
patch 1, 3-8 do not interfere with the UBER patch. Patches look good to me.
Reviewed-by: Mark Tinguely <tinguely@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-20 22:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 22:40 [PATCH 0/8] xfsprogs: misc small fixes Eric Sandeen
2013-01-26 22:40 ` [PATCH 1/8] libhandle: Guard against string overflow in path_to_fspath() Eric Sandeen
2013-01-26 22:40 ` [PATCH 2/8] libxfs: initialize xfs_alloc_arg structures Eric Sandeen
2013-01-28 0:35 ` Dave Chinner
2013-01-28 2:41 ` Eric Sandeen
2013-01-29 18:49 ` Ben Myers
2013-01-28 14:21 ` Mark Tinguely
2013-01-26 22:40 ` [PATCH 3/8] libxfs: fix setup_cursor array allocation Eric Sandeen
2013-01-26 22:40 ` [PATCH 4/8] xfs_repair: Fix free of uninit ptr in xfs_acl_valid() error path Eric Sandeen
2013-01-26 22:40 ` [PATCH 5/8] xfs_fsr: guard against path string overflows Eric Sandeen
2013-01-26 22:40 ` [PATCH 6/8] xfs_fsr: check strdup results properly in initallfs() Eric Sandeen
2013-01-26 22:40 ` [PATCH 7/8] xfs_fsr: fix attribute no_change_count logic Eric Sandeen
2013-01-26 22:40 ` [PATCH 8/8] xfs_fsr: remove extraneous close() in fsrallfs() Eric Sandeen
2013-02-20 22:09 ` Mark Tinguely [this message]
2013-02-21 17:02 ` [PATCH 0/8] xfsprogs: misc small fixes Mark Tinguely
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=512549B6.70705@sgi.com \
--to=tinguely@sgi.com \
--cc=sandeen@redhat.com \
--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