Hello Greg,
Here are trivial backports for upstream commit, which is tagged as stable:
02a3307aa9c2 ("btrfs: fix reading stale metadata blocks after degraded raid1 mounts")
Regards, Nikolay
On Mon, May 21, 2018 at 10:18:00AM +0300, Nikolay Borisov wrote:
Hello Greg,
Here are trivial backports for upstream commit, which is tagged as stable:
02a3307aa9c2 ("btrfs: fix reading stale metadata blocks after degraded raid1 mounts")
What about 4.16?
thanks,
greg k-h
On 21.05.2018 11:24, Greg KH wrote:
On Mon, May 21, 2018 at 10:18:00AM +0300, Nikolay Borisov wrote:
Hello Greg,
Here are trivial backports for upstream commit, which is tagged as stable:
02a3307aa9c2 ("btrfs: fix reading stale metadata blocks after degraded raid1 mounts")
What about 4.16?
I only provided patches for LTS releases. In any case, the code in question hasn't changed recently so the 4.14 backport should apply to 4.16.
thanks,
greg k-h
On Mon, May 21, 2018 at 11:27:37AM +0300, Nikolay Borisov wrote:
On 21.05.2018 11:24, Greg KH wrote:
On Mon, May 21, 2018 at 10:18:00AM +0300, Nikolay Borisov wrote:
Hello Greg,
Here are trivial backports for upstream commit, which is tagged as stable:
02a3307aa9c2 ("btrfs: fix reading stale metadata blocks after degraded raid1 mounts")
What about 4.16?
I only provided patches for LTS releases. In any case, the code in question hasn't changed recently so the 4.14 backport should apply to 4.16.
I don't want someone moving from a 4.14-lts release to 4.16 to hit a regression, that would be foolish :)
Anyway, thanks, I'll take the 4.14 backport.
greg k-h
On Mon, May 21, 2018 at 10:18:00AM +0300, Nikolay Borisov wrote:
Hello Greg,
Here are trivial backports for upstream commit, which is tagged as stable:
02a3307aa9c2 ("btrfs: fix reading stale metadata blocks after degraded raid1 mounts")
the 4.9 and 4.4 patches break the build :(
Please test build them at the least...
greg k-h
On 21.05.2018 11:47, Greg KH wrote:
On Mon, May 21, 2018 at 10:18:00AM +0300, Nikolay Borisov wrote:
Hello Greg,
Here are trivial backports for upstream commit, which is tagged as stable:
02a3307aa9c2 ("btrfs: fix reading stale metadata blocks after degraded raid1 mounts")
the 4.9 and 4.4 patches break the build :(
Huhz, I tested on 4.14 and it was ok so I assumed other will be as well.
Nothing works as expected on Mondays .....
On it!
Please test build them at the least...
greg k-h
On 21.05.2018 11:47, Greg KH wrote:
On Mon, May 21, 2018 at 10:18:00AM +0300, Nikolay Borisov wrote:
Hello Greg,
Here are trivial backports for upstream commit, which is tagged as stable:
02a3307aa9c2 ("btrfs: fix reading stale metadata blocks after degraded raid1 mounts")
the 4.9 and 4.4 patches break the build :(
Please test build them at the least...
Fixed and test-built on both kernel versions!
greg k-h
On Mon, May 21, 2018 at 12:00:15PM +0300, Nikolay Borisov wrote:
On 21.05.2018 11:47, Greg KH wrote:
On Mon, May 21, 2018 at 10:18:00AM +0300, Nikolay Borisov wrote:
Hello Greg,
Here are trivial backports for upstream commit, which is tagged as stable:
02a3307aa9c2 ("btrfs: fix reading stale metadata blocks after degraded raid1 mounts")
the 4.9 and 4.4 patches break the build :(
Please test build them at the least...
Fixed and test-built on both kernel versions!
Many thanks, now queued up.
greg k-h
linux-stable-mirror@lists.linaro.org