From: <gregkh@linuxfoundation.org>
To: darrick.wong@oracle.com, bfoster@redhat.com,
gregkh@linuxfoundation.org, hch@lst.de
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "xfs: actually report xattr extents via iomap" has been added to the 4.11-stable tree
Date: Mon, 05 Jun 2017 17:07:48 +0200 [thread overview]
Message-ID: <149667526817214@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
xfs: actually report xattr extents via iomap
to the 4.11-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
xfs-actually-report-xattr-extents-via-iomap.patch
and it can be found in the queue-4.11 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From 84358536dc355a9c8978ee425f87e116186bed16 Mon Sep 17 00:00:00 2001
From: "Darrick J. Wong" <darrick.wong@oracle.com>
Date: Thu, 6 Apr 2017 16:00:39 -0700
Subject: xfs: actually report xattr extents via iomap
From: Darrick J. Wong <darrick.wong@oracle.com>
commit 84358536dc355a9c8978ee425f87e116186bed16 upstream.
Apparently FIEMAP for xattrs has been broken since we switched to
the iomap backend because of an incorrect check for xattr presence.
Also fix the broken locking.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
fs/xfs/xfs_iomap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/fs/xfs/xfs_iomap.c
+++ b/fs/xfs/xfs_iomap.c
@@ -1170,10 +1170,10 @@ xfs_xattr_iomap_begin(
if (XFS_FORCED_SHUTDOWN(mp))
return -EIO;
- lockmode = xfs_ilock_data_map_shared(ip);
+ lockmode = xfs_ilock_attr_map_shared(ip);
/* if there are no attribute fork or extents, return ENOENT */
- if (XFS_IFORK_Q(ip) || !ip->i_d.di_anextents) {
+ if (!XFS_IFORK_Q(ip) || !ip->i_d.di_anextents) {
error = -ENOENT;
goto out_unlock;
}
Patches currently in stable-queue which might be from darrick.wong@oracle.com are
queue-4.11/xfs-fix-missed-holes-in-seek_hole-implementation.patch
queue-4.11/xfs-fix-indlen-accounting-error-on-partial-delalloc-conversion.patch
queue-4.11/xfs-fix-over-copying-of-getbmap-parameters-from-userspace.patch
queue-4.11/xfs-bad-assertion-for-delalloc-an-extent-that-start-at-i_size.patch
queue-4.11/xfs-bmapx-shouldn-t-barf-on-inline-format-directories.patch
queue-4.11/xfs-drop-iolock-from-reclaim-context-to-appease-lockdep.patch
queue-4.11/mm-avoid-spurious-bad-pmd-warning-messages.patch
queue-4.11/xfs-fix-off-by-one-on-max-nr_pages-in-xfs_find_get_desired_pgoff.patch
queue-4.11/xfs-update-ag-iterator-to-support-wait-on-new-inodes.patch
queue-4.11/xfs-use-dedicated-log-worker-wq-to-avoid-deadlock-with-cil-wq.patch
queue-4.11/xfs-fix-up-quotacheck-buffer-list-error-handling.patch
queue-4.11/xfs-wait-on-new-inodes-during-quotaoff-dquot-release.patch
queue-4.11/dax-fix-race-between-colliding-pmd-pte-entries.patch
queue-4.11/xfs-use-b_state-to-fix-buffer-i-o-accounting-release-race.patch
queue-4.11/xfs-avoid-mount-time-deadlock-in-cow-extent-recovery.patch
queue-4.11/xfs-fix-off-by-in-in-loop-termination-in-xfs_find_get_desired_pgoff.patch
queue-4.11/xfs-xfs_trans_alloc_empty.patch
queue-4.11/xfs-fix-integer-truncation-in-xfs_bmap_remap_alloc.patch
queue-4.11/xfs-actually-report-xattr-extents-via-iomap.patch
queue-4.11/xfs-fix-use-after-free-in-xfs_finish_page_writeback.patch
queue-4.11/xfs-reserve-enough-blocks-to-handle-btree-splits-when-remapping.patch
queue-4.11/xfs-support-ability-to-wait-on-new-inodes.patch
queue-4.11/xfs-prevent-multi-fsb-dir-readahead-from-reading-random-blocks.patch
queue-4.11/xfs-fix-unaligned-access-in-xfs_btree_visit_blocks.patch
queue-4.11/xfs-handle-array-index-overrun-in-xfs_dir2_leaf_readbuf.patch
reply other threads:[~2017-06-05 15:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=149667526817214@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.