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: Mon, 30 Jul 2018 08:09:33 +0200 [thread overview]
Message-ID: <d2e9d4d2-92d8-0ec7-ab85-c264ffba1351@contabo.de> (raw)
In-Reply-To: <20180727225850.GC229060@rodete-desktop-imager.corp.google.com>
On 07/28/2018 12:58 AM, Minchan Kim wrote:
> I made a mistake on previous patch.
> Could you test this patches?
Thanks! Looking good so far! No errors whatsoever with the new patch. I
will let my test workload running for while to be sure, but I think we
are good.
--
Kind regards,
Tino Lehnig
next prev parent reply other threads:[~2018-07-30 6:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 12:29 Zram writeback feature unstable with heavy swap utilization - BUG: Bad page state in process 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
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 [this message]
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=d2e9d4d2-92d8-0ec7-ab85-c264ffba1351@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.