Hi Ted,
On Wed, 29 May 2019 at 09:26, Theodore Ts'o <tytso(a)mit.edu> wrote:
>
> On Wed, May 29, 2019 at 10:52:56AM +0800, kernel test robot wrote:
> > FYI, we noticed the following commit (built with gcc-7):
> >
> > commit: 079f9927c7bfa026d963db1455197159ebe5b534 ("ext4: gracefully handle ext4_break_layouts() failure during truncate")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
I do have found this problem on linux next 20190528 on x86_64, i386,
arm64 and arm architectures.
But, this failure is not easy to reproduce.
so thought of sharing report with steps to reproduce and got delayed.
>
> Jan --- this is the old version of your patch, which I had dropped
> before sending a push request to Linus. However, I forgot to reset
> the dev branch so it still had the old patch on it, and so it got
> picked up in linux-next. Apologies for the confusion.
>
> I've reset the dev branch on ext4.git, and the new version of your
> patch will show up there shortly, as I start reviewing patches for the
> next merge window.
However, Thanks for looking into this problem.
I will keep monitoring this mmap16 failure and let you know when it
will get fixed.
- Naresh
Do you see test VIDIOC_G/S_PARM: FAIL on stable 4.14, 4.9 and 4.4
kernel branches ?
test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: OK
fail: ../../../v4l-utils-1.16.0/utils/v4l2-compliance/v4l2-test-formats.cpp(1132):
reserved not zeroed
test VIDIOC_G/S_PARM: FAIL
Test passes on mainline, -next, 5.0 and 4.19
Test failed on 4.14, 4.9 and 4.4
steps to reproduce:
# boot any 4.9/4.14 kernel on x86_64 / Juno / hikey device
# install v4l-utils package
# modprobe vivid.ko no_error_inj=1
# v4l2-compliance -v -d /dev/video0
Full test log,
https://lkft.validation.linaro.org/scheduler/job/708755#L1791
Test results comparison on all branches,
https://qa-reports.linaro.org/_/comparetest/?project=22&project=6&project=5…
Best Regards
Naresh Kamboju