From: Tino Lehnig <tino.lehnig@contabo.de>
To: Minchan Kim <minchan@kernel.org>
Cc: ngupta@vflare.org, linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Zram writeback feature unstable with heavy swap utilization - BUG: Bad page state in process...
Date: Thu, 26 Jul 2018 12:00:44 +0200 [thread overview]
Message-ID: <15e3a0af-7e02-83fb-4b72-b05f6d7ded71@contabo.de> (raw)
In-Reply-To: <1684cefc-c920-d53c-8d2d-c32da213a045@contabo.de>
On 07/26/2018 08:10 AM, Tino Lehnig wrote:
>> A thing I could imagine is
>> [0bcac06f27d75, skip swapcache for swapin of synchronous device]
>> It was merged into v4.15. Could you check it by bisecting?
>
> Thanks, I will check that.
So I get the same behavior as in v4.15-rc1 after this commit. All prior
builds are fine.
I have also tested all other 4.15 rc builds now and the symptoms are the
same through rc8. KVM processes become unresponsive and I see kernel
messages like the one below. This happens with and without the writeback
feature being used. The bad page state bug appears very rarely in these
versions and only when writeback is active.
Starting with rc9, I only get the same bad page state bug as in all
newer kernels.
--
[ 363.494793] INFO: task kworker/4:2:498 blocked for more than 120 seconds.
[ 363.494872] Not tainted 4.14.0-zram-pre-rc1 #17
[ 363.494943] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[ 363.495021] kworker/4:2 D 0 498 2 0x80000000
[ 363.495029] Workqueue: events async_pf_execute
[ 363.495030] Call Trace:
[ 363.495037] ? __schedule+0x3bc/0x830
[ 363.495039] schedule+0x32/0x80
[ 363.495042] io_schedule+0x12/0x40
[ 363.495045] __lock_page_or_retry+0x302/0x320
[ 363.495047] ? page_cache_tree_insert+0xa0/0xa0
[ 363.495051] do_swap_page+0x4ab/0x860
[ 363.495054] __handle_mm_fault+0x77b/0x10c0
[ 363.495056] handle_mm_fault+0xc6/0x1b0
[ 363.495059] __get_user_pages+0xf9/0x620
[ 363.495061] ? update_load_avg+0x5d6/0x6d0
[ 363.495064] get_user_pages_remote+0x137/0x1f0
[ 363.495067] async_pf_execute+0x62/0x180
[ 363.495071] process_one_work+0x184/0x380
[ 363.495073] worker_thread+0x4d/0x3c0
[ 363.495076] kthread+0xf5/0x130
[ 363.495078] ? process_one_work+0x380/0x380
[ 363.495080] ? kthread_create_worker_on_cpu+0x50/0x50
[ 363.495083] ? do_group_exit+0x3a/0xa0
[ 363.495086] ret_from_fork+0x1f/0x30
--
Kind regards,
Tino Lehnig
next prev parent reply other threads:[~2018-07-26 10:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 12:29 Tino Lehnig
2018-07-24 1:03 ` Minchan Kim
2018-07-24 2:53 ` Sergey Senozhatsky
2018-07-24 6:47 ` Minchan Kim
2018-07-24 7:30 ` Tino Lehnig
2018-07-25 1:32 ` Minchan Kim
2018-07-25 1:55 ` Matthew Wilcox
2018-07-25 2:16 ` Minchan Kim
2018-07-25 2:35 ` Matthew Wilcox
2018-07-25 2:51 ` Minchan Kim
2018-07-25 2:55 ` Matthew Wilcox
2018-07-25 3:02 ` Minchan Kim
2018-07-25 2:51 ` Matthew Wilcox
2018-07-25 4:07 ` Sergey Senozhatsky
2018-07-25 13:21 ` Minchan Kim
2018-07-25 15:12 ` Tino Lehnig
2018-07-26 2:03 ` Minchan Kim
2018-07-26 6:10 ` Tino Lehnig
2018-07-26 6:21 ` Minchan Kim
2018-07-26 6:34 ` Tino Lehnig
2018-07-26 10:00 ` Tino Lehnig [this message]
2018-07-26 10:30 ` Minchan Kim
2018-07-26 12:35 ` Tino Lehnig
2018-07-27 9:14 ` Minchan Kim
2018-07-27 11:00 ` Tino Lehnig
2018-07-27 12:05 ` Minchan Kim
2018-07-27 12:13 ` Tino Lehnig
2018-07-27 22:58 ` Minchan Kim
2018-07-30 6:09 ` Tino Lehnig
2018-08-02 5:15 ` Minchan Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15e3a0af-7e02-83fb-4b72-b05f6d7ded71@contabo.de \
--to=tino.lehnig@contabo.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®