On Tue, 26 Mar 2024 at 18:07, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote: > > On Mon, 25 Mar 2024 at 17:29, Sasha Levin <sashal@xxxxxxxxxx> wrote: > > > > > > This is the start of the stable review cycle for the 4.19.311 release. > > There are 147 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Mar 27 11:58:33 AM UTC 2024. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-4.19.y&id2=v4.19.310 > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y > > and the diffstat can be found below. > > > > Thanks, > > Sasha > > One more important update from Linaro LKFT testing, > > LTP syscalls fallocate06 fails on qemu-arm64 and juno-r2 devices. > > fallocate06.c:155: TFAIL: fallocate(FALLOC_FL_PUNCH_HOLE | > FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (28) > > Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx> > > We are running bisections on this issue and get back to you. This is to confirm that the reported issue is not a kernel regression. The reason is due to updates on userspace tools regarding the btrfs. - Naresh
