Bug 191761
Summary: | forced readonly, fs/btrfs/delayed-inode.c:1170 __btrfs_run_delayed_items | ||
---|---|---|---|
Product: | File System | Reporter: | Chris Murphy (bugzilla) |
Component: | btrfs | Assignee: | Josef Bacik (josef) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | ||
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 4.10-rc3 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: |
dmesg
git bisect log |
Description
Chris Murphy
2017-01-02 20:40:05 UTC
Problem continues with these tested kernels: kernel-4.9.2-200.fc25.x86_64 kernel-4.10.0-0.rc3.git0.1.fc26.x86_64 Created attachment 251271 [details] git bisect log git bisect says # first bad commit: [6c6ef9f26e598fb977f60935e109cd5b266c941a] xattr: Stop calling {get,set,remove}xattr inode operations Then I did [chris@f25h linux]$ git checkout 6c6ef9f26e598fb977f60935e109cd5b266c941a~ HEAD is now at bf3ee71... vfs: Check for the IOP_XATTR flag in listxattr Problem does not happen with this kernel. Found this https://lkml.org/lkml/2016/11/3/268 but those patches appear to be in 4.10-rc3 so there's still something causing problems on *certain* Btrfs subvolumes/snapshots; maybe what's happened is a prior kernel with a problem (same problem? different problem?) has somehow affected those snapshots in a way that causes this commit to trip things up in Btrfs? Upstream thread https://www.spinics.net/lists/linux-btrfs/msg62368.html Patch https://www.spinics.net/lists/linux-btrfs/msg62362.html Should make it into stable. |