Yes the test results indicates that data was read cached using fscache
and 960948 ops have gone through the change.
we are not planning to test with 4.4.0-139 kernel as I don't have a
system setup for this kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
test log attached
** Attachment added: "test log for fscache page leak."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793430/+attachment/5199707/+files/fscache_page_leak_test.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yes we were able to test with 4.15.0-37-generic kernel aswell.
Your sosreport has been generated and saved in:
/tmp/sosreport-kmodukuri.00195310-20181010154537.tar.xz
The checksum is: 8c057643e9995694678915ce550e422c
Please send this file to your support representative.
** Attachment added:
All tests passed from Nvidia testing for fscache.
Your sosreport has been generated and saved in:
/tmp/sosreport-tid1870983.00195310-20181009172638.tar.xz
The checksum is: 2f7b671685cf8116920efb63e6397fe2
** Attachment added: "sosreport-tid1870983.00195310-20181009172638.tar.xz"
we are trying to get hardware resource to test this before 10/9. will
keep you posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793430
Title:
Page leaking in cachefiles_read_backing_file
Public bug reported:
== SRU Justification ==
[Impact]
Oops during heavy NFS + FSCache + Cachefiles use:
kernel BUG at /build/linux-Y09MKI/linux-4.4.0/fs/fscache/internal.h:321!
kernel BUG at /build/linux-Y09MKI/linux-4.4.0/fs/fscache/cookie.c:639!
[Cause]
1)Two threads are trying to do
Public bug reported:
== SRU Justification ==
[Impact]
Oops during heavy NFS + FSCache + Cachefiles use:
CacheFiles: Error: Overlong wait for old active object to go away.
BUG: unable to handle kernel NULL pointer dereference at 0002
CacheFiles: Error: Object already active
