From: "Agustín DallʼAlba" <agustin@dallalba.com.ar>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>, Linux-MM <linux-mm@kvack.org>,
Henry Burns <henrywolfeburns@gmail.com>
Subject: Re: CRASH: General protection fault in z3fold
Date: Mon, 09 Sep 2019 19:59:30 -0300 [thread overview]
Message-ID: <28453b3deba00d9343fdcbde5bcda00e7615d321.camel@dallalba.com.ar> (raw)
In-Reply-To: <CAMJBoFNa3w5zHwM8QOUgr-UUctKnXn3b6SzeZ5MB5CXDdS3wwg@mail.gmail.com>
On Mon, 2019-09-09 at 14:44 +0200, Vitaly Wool wrote:
> On Mon, Sep 9, 2019 at 9:17 AM Vitaly Wool <vitalywool@gmail.com> wrote:
> > On Mon, Sep 9, 2019 at 2:14 AM Agustín DallʼAlba <agustin@dallalba.com.ar> wrote:
> > > However trace 2 (__zswap_pool_release blocked for more than xxxx
> > > seconds) still happens.
> >
> > That one is pretty new and seems to have been caused by
> > d776aaa9895eb6eb770908e899cb7f5bd5025b3c ("mm/z3fold.c: fix race
> > between migration and destruction").
> > I'm looking into this now and CC'ing Henry just in case.
>
> Agustin, could you please try reverting that commit? I don't think
> it's working as it should.
>
> > ~Vitaly
I reverted the commit and I haven't seen the deadlock happen again.
Should I be experiencing some side effect of having reverted that?
Thanks,
Agustín
next prev parent reply other threads:[~2019-09-09 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 4:05 Agustín DallʼAlba
2019-09-05 11:55 ` Vlastimil Babka
2019-09-08 11:09 ` Vitaly Wool
2019-09-09 0:14 ` Agustín DallʼAlba
2019-09-09 7:17 ` Vitaly Wool
2019-09-09 12:44 ` Vitaly Wool
2019-09-09 17:51 ` Henry Burns
2019-09-09 22:59 ` Agustín DallʼAlba [this message]
2019-09-10 1:08 ` Henry Burns
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=28453b3deba00d9343fdcbde5bcda00e7615d321.camel@dallalba.com.ar \
--to=agustin@dallalba.com.ar \
--cc=ddstreet@ieee.org \
--cc=henrywolfeburns@gmail.com \
--cc=linux-mm@kvack.org \
--cc=sjenning@redhat.com \
--cc=vbabka@suse.cz \
--cc=vitalywool@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