Bug 1740690
| Summary: | zswap z3fold BUG: unable to handle page fault for address or GPF z3fold_zpool_malloc or z3fold_zpool_map | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Markus Linnala <markus.linnala> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 30 | CC: | airlied, bskeggs, bugzilla, hdegoede, ichavero, itamar, jarodwilson, jeremy, jforbes, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, masami256, mchehab, mjg59, steved |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-21 15:11:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Markus Linnala
2019-08-13 13:35:29 UTC
Created attachment 1603385 [details]
dmesg-zswap-z3fold_zpool_map-5.2.8-200.fc30.x86_64.txt
z3fold_zpool_map variant with 5.2.8-200.fc30.x86_64
Created attachment 1603386 [details]
dmesg-zswap-z3fold_zpool_malloc-5.2.8-200.fc30.x86_64.txt
z3fold_zpool_malloc variant with 5.2.8-200.fc30.x86_64
Created attachment 1603388 [details]
dmesg-zswap-writeback_entry-5.2.8-200.fc30.x86_64.txt
zswap_writeback_entry variant using 5.2.8-200.fc30.x86_64
I got this after I ran: pkill stress
This needs to be reported to the upstream maintainers, Fedora isn't using any custom patches here. $ ./scripts/get_maintainer.pl -f mm/zswap.c Seth Jennings <sjenning> (maintainer:ZSWAP COMPRESSED SWAP CACHING) Dan Streetman <ddstreet> (maintainer:ZSWAP COMPRESSED SWAP CACHING) linux-mm (open list:ZSWAP COMPRESSED SWAP CACHING) linux-kernel.org (open list) Created attachment 1603389 [details]
dmesg-zswap-5.2.8-200.fc30.x86_64.txt
Normal boot with 5.2.8-200.fc30.x86_64
There is at least one recent patch about z3fold issues: https://lkml.org/lkml/2019/8/9/758 Created attachment 1603431 [details]
dmesg-zswap-z3fold_zpool_free-5.1.20.txt
Seems I can get issues with 5.1.20 too, but maybe issue is different.
I have found issue twice now. Of one I lost start of logs because too much info.
First time it took about 20 minutes to get issue and second time about 8 minutes.
With 5.2.8 sometimes problems start within seconds of starting stress job.
5.0.20-200.fc29.x86_64 seemd to survive 1.5h until I stopped. Also 5.1.0-300.fc30.x86_64 survived 1.5h until I stopped. I did git bisect run from v5.1 (good) v5.3-rc4 (bad) and got this:
7c2b8baa61fe578af905342938ad12f8dbaeae79 is the first bad commit
commit 7c2b8baa61fe578af905342938ad12f8dbaeae79
Author: Vitaly Wool <...>
Date: Mon May 13 17:22:49 2019 -0700
mm/z3fold.c: add structure for buddy handles
For z3fold to be able to move its pages per request of the memory
subsystem, it should not use direct object addresses in handles. Instead,
it will create abstract handles (3 per page) which will contain pointers
to z3fold objects. Thus, it will be possible to change these pointers
when z3fold page is moved.
Link: http://lkml.kernel.org/r/20190417103826.484eaf18c1294d682769880f@gmail.com
Signed-off-by: Vitaly Wool <...>
Cc: Bartlomiej Zolnierkiewicz <...>
Cc: Dan Streetman <...>
Cc: Krzysztof Kozlowski <...>
Cc: Oleksiy Avramchenko <...>
Cc: Uladzislau Rezki <...>
Signed-off-by: Andrew Morton <...>
Signed-off-by: Linus Torvalds <...>
:040000 040000 1a27b311b3ad8556062e45fff84d46a57ba8a4b1 a79e463e14ab8ea271a89fb5f3069c3c84221478 M mm
bisect run success
I used this as test program:
stress --vm $(($(nproc)+2)) --vm-bytes $(($(awk '/MemAvail/{print $2}' /proc/meminfo)*1024/$(nproc))) --timeout 900
I'm not seeing a field for upstream bugs so I'm leaving this here... https://bugzilla.kernel.org/show_bug.cgi?id=204563 This issue is handled by upstream in at least kernel 5.3.11 or earlier. I'll close it. Fix resolution |