From: Eric Sandeen <sandeen@redhat.com>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: [PATCH 0/2] xfs: AGI buffer type handling
Date: Wed, 30 Nov 2016 16:36:25 -0600 [thread overview]
Message-ID: <203e6e5c-7663-b49b-36af-5885aa1f461a@redhat.com> (raw)
We were missing a xfs_trans_buf_set_type() to XFS_BLFT_AGI_BUF
in xlog_recover_clear_agi_bucket.
Fix this in 2 stages; first simply add it to this function for
simple -stable backports, then move all of them into
xfs_read_agi() so it doesn't get forgotten again.
-Eric
next reply other threads:[~2016-11-30 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 22:36 Eric Sandeen [this message]
2016-11-30 22:40 ` [PATCH 1/2] xfs: set AGI buffer type in xlog_recover_clear_agi_bucket Eric Sandeen
2016-12-01 12:15 ` Brian Foster
2016-12-02 13:15 ` Christoph Hellwig
2016-11-30 22:42 ` [PATCH 2/2] xfs: Move AGI buffer type setting to xfs_read_agi Eric Sandeen
2016-12-01 12:15 ` Brian Foster
2016-12-01 17:43 ` [PATCH 2/2 V2] " Eric Sandeen
2016-12-02 13:16 ` 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=203e6e5c-7663-b49b-36af-5885aa1f461a@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).