From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfs: regression fixes
Date: Tue, 27 May 2014 08:26:52 +1000 [thread overview]
Message-ID: <1401143214-9181-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
These are a couple of fixes that have come to light in the past few
days. The first prevents bad things happening in memory reclaim
when kswapd delegates block allocation to a workqueue, and the
second ensures XFS doesn't incorrectly try to check the sector size
on non-xfs devices when mount is probing.
Both are regressions, but given how late in the 3.15 cycle we are,
I'll probably just push these through the 3.16 merge to give them a
bit more testing and let them be handled by stable kernel backports.
Anyone have any particular concerns over that plan?
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-05-26 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 22:26 Dave Chinner [this message]
2014-05-26 22:26 ` [PATCH 1/2] xfs: block allocation work needs to be kswapd aware Dave Chinner
2014-05-27 10:38 ` Christoph Hellwig
2014-05-26 22:26 ` [PATCH 2/2] xfs: xfs_readsb needs to check for magic numbers Dave Chinner
2014-05-27 10:40 ` Christoph Hellwig
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=1401143214-9181-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.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