From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfs: misc. attribute and log recovery fixes
Date: Thu, 18 Jun 2015 08:48:59 -0400 [thread overview]
Message-ID: <1434631741-50856-1-git-send-email-bfoster@redhat.com> (raw)
Hi all,
This is just a couple miscellaneous fixes. Patch 1 fixes a regression in
the attribute fork destruction path in xfs_inactive(). Considering that
the cause of said regression was stable fodder, this might be as well.
Patch 2 fixes a crash reproduced on an s390x box due to a memcpy()
overflow in log recovery due to a corrupted log operation header (caused
by fsfuzzer).
Thoughts, reviews, flames appreciated.
Brian
Brian Foster (2):
xfs: don't truncate attribute extents if no extents exist
xfs: validate transaction header length on log recovery
fs/xfs/xfs_attr_inactive.c | 3 ++-
fs/xfs/xfs_log_recover.c | 10 ++++++++--
2 files changed, 10 insertions(+), 3 deletions(-)
--
1.9.3
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-06-18 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 12:48 Brian Foster [this message]
2015-06-18 12:49 ` [PATCH 1/2] xfs: don't truncate attribute extents if no extents exist Brian Foster
2015-06-19 15:14 ` Christoph Hellwig
2015-06-19 15:45 ` Brian Foster
2015-06-21 9:22 ` Christoph Hellwig
2015-06-22 13:38 ` [PATCH v2] " Brian Foster
2015-06-18 12:49 ` [PATCH 2/2] xfs: validate transaction header length on log recovery Brian Foster
2015-06-21 9:27 ` Christoph Hellwig
2015-06-21 20:25 ` Brian Foster
2015-06-21 23:05 ` Dave Chinner
2015-06-22 13:59 ` Brian Foster
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=1434631741-50856-1-git-send-email-bfoster@redhat.com \
--to=bfoster@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