linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-mm@kvack.org, linux-xfs@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org, goodmirek@goodmirek.com,
	Hillf Danton <hillf.zj@alibaba-inc.com>,
	Dmitry Vyukov <dvyukov@gmail.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Subject: Re: [Bug 205135] System hang up when memory swapping (kswapd deadlock)
Date: Tue, 22 Oct 2019 15:24:22 -0700	[thread overview]
Message-ID: <20191022152422.e47fda82879dc7cd1f3cf5e5@linux-foundation.org> (raw)
In-Reply-To: <bug-205135-27-vbbrgnF9A3@https.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Tue, 22 Oct 2019 09:02:22 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=205135
> 
> --- Comment #7 from goodmirek@goodmirek.com ---
> Everyone who uses a swapfile on XFS filesystem seem affected by this hang up.
> Not sure about other filesystems, I did not have a chance to test it elsewhere.
> 
> This unreproduced bot crash could be related:
> https://lore.kernel.org/linux-mm/20190910071804.2944-1-hdanton@sina.com/

Thanks.  Might be core MM, might be XFS, might be Fedora.

Hilf, does your patch look related?  That seems to have gone quiet?

Should we progress Tetsuo's patch?


       reply	other threads:[~2019-10-22 22:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-205135-27@https.bugzilla.kernel.org/>
     [not found] ` <bug-205135-27-vbbrgnF9A3@https.bugzilla.kernel.org/>
2019-10-22 22:24   ` Andrew Morton [this message]
2019-10-23  1:22     ` [Bug 205135] System hang up when memory swapping (kswapd deadlock) Darrick J. Wong
2019-10-23  2:37       ` Su Yue
2019-10-23  6:49       ` Dave Chinner
2019-10-23  7:12         ` Dave Chinner

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=20191022152422.e47fda82879dc7cd1f3cf5e5@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dvyukov@gmail.com \
    --cc=goodmirek@goodmirek.com \
    --cc=hillf.zj@alibaba-inc.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    /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;
as well as URLs for NNTP newsgroup(s).