From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfs: fix a couple post-merge sparse inode chunks issues
Date: Mon, 1 Jun 2015 10:33:12 -0400 [thread overview]
Message-ID: <1433169194-41808-1-git-send-email-bfoster@redhat.com> (raw)
Hi all,
Here are a couple quick hitter fixes for sparse inodes. Patch 1 fixes a
compile failure detected by the kbuild robot with 32-bit configs. Patch
2 fixes a problem with the DEBUG mode random sparse inode chunk
allocation on large block size filesystems.
Brian
Brian Foster (2):
xfs: fix sparse inodes 32-bit compile failure
xfs: check min blks for random debug mode sparse allocations
fs/xfs/libxfs/xfs_ialloc.c | 15 ++++++++-------
fs/xfs/xfs_inode.c | 2 +-
2 files changed, 9 insertions(+), 8 deletions(-)
--
1.9.3
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-06-01 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 14:33 Brian Foster [this message]
2015-06-01 14:33 ` [PATCH 1/2] xfs: fix sparse inodes 32-bit compile failure Brian Foster
2015-06-01 20:52 ` Dave Chinner
2015-06-01 21:16 ` [PATCH v2] " Brian Foster
2015-06-01 14:33 ` [PATCH 2/2] xfs: check min blks for random debug mode sparse allocations 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=1433169194-41808-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