xfs: put metadata inodes in a separate lockdep class

Metadata inodes are not supposed to be exposed to userspace, which
eliminates most conflicts with vfs rwseasm, page cache locks, etc.  This
means that we actually /can/ do things like copy data to userspace while
holding a metadata inode's ILOCK, since, uh.... well what happens if we
copy rt fsmap data to an rt file, which then causes an rt allocation and
therfore needs the rtrmap ilock...?

Confused-by: Darrick J. Wong <darrick.wong@oracle.com>

0 files changed, 0 insertions, 0 deletions