On Mon, Jun 23, 2014 at 06:49:14PM +0200, David Sterba wrote:
> > Also, any of these relevant to any older stable kernels?
>
> Most of them are relevant for 3.14 at least. A quick check shows that
> this patchset does not apply cleanly. I'll let you know the good commit
> ids.
For 3.14 (apply cleanly on top of 3.14.8):
Subjects:
btrfs: Add ctime/mtime update for btrfs device add/remove.
Btrfs: output warning instead of error when loading free space cache failed
Btrfs: make sure there are not any read requests before stopping workers
Btrfs: fix NULL pointer crash of deleting a seed device
Btrfs: mark mapping with error flag to report errors to userspace
Btrfs: set right total device count for seeding support
Btrfs: fix double free in find_lock_delalloc_range
Btrfs: send, don't error in the presence of subvols/snapshots
fs: btrfs: volumes.c: Fix for possible null pointer dereference
Btrfs: don't check nodes for extent items
Btrfs: use right type to get real comparison
Btrfs: fix scrub_print_warning to handle skinny metadata extents
btrfs: fix use of uninit "ret" in end_extent_writepage()
Commits:
5a1972bd9fd4b2fb1bac8b7a0b636d633d8717e3
32d6b47fe6fc1714d5f1bba1b9f38e0ab0ad58a8
de348ee022175401e77d7662b7ca6e231a94e3fd
29cc83f69c8338ff8fd1383c9be263d4bdf52d73
5dca6eea91653e9949ce6eb9e9acab6277e2f2c4
298658414a2f0bea1f05a81876a45c1cd96aa2e0
7d78874273463a784759916fc3e0b4e2eb141c70
1af56070e3ef9477dbc7eba3b9ad7446979c7974
8321cf2596d283821acc466377c2b85bcd3422b7
8a56457f5f8fa7c2698ffae8545214c5b96a2cb5
cd857dd6bc2ae9ecea14e75a34e8a8fdc158e307
6eda71d0c030af0fc2f68aaa676e6d445600855b
3e2426bd0eb980648449e7a2f5a23e3cd3c7725c
The send related patches depend on other fixes from 3.15, were dropped.
The remaining patch needs another one to apply cleanly:
Subjects:
btrfs: fix lockdep warning with reclaim lock inversion
btrfs: allocate raid type kobjects dynamically
Commits:
ed55b6ac077fe7f9c6490ff55172c4b563562d7c
c1895442be01c58449e3bf9272f22062a670e08f
The commit ids apply without conflicts in the order of appearance in
this mail.
I haven't looked at older stable kernels, this would require more time
than I'm currently able to spend on it. It's possible that some patches
apply though.
Thanks,
david
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html