From: Oleg Nesterov <oleg@redhat.com>
To: Nikolay Borisov <kernel@kyup.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: BUG_ON in rcu_sync_func triggered
Date: Tue, 13 Sep 2016 17:20:42 +0200 [thread overview]
Message-ID: <20160913152042.GA30160@redhat.com> (raw)
In-Reply-To: <57D80F52.6090804@kyup.com>
On 09/13, Nikolay Borisov wrote:
>
> On 09/13/2016 05:35 PM, Nikolay Borisov wrote:
> >
> > On 09/13/2016 04:43 PM, Oleg Nesterov wrote:
> >> On 09/13, Oleg Nesterov wrote:
> >>>
> >>> OK... perhaps the unbalanced up_write... I'll try to look at freeze/thaw code,
> >>
> >> Heh, yes, it looks racy or I am totally confused.
> >>
> >>> could test the debugging patch below meanwhile?
> >>
> >> Yes please. I'll send you another patch (hopefully fix) later, but it
> >> would be nice if you can test this patch to get more info.
> >
> > I've already started testing with this patch on 4.4.20 this time
I think it would be better to stay with the same kernel version to
debug the problem...
> Actually forget that, here is a warning that this triggered:
>
> [ 844.290454] WARNING: CPU: 2 PID: 1900 at kernel/rcu/sync.c:160 rcu_sync_func+0xc8/0x150()
> ...
> [ 844.754708] XXX: ffff88047527da78 gp=2 cnt=0 cb=1
Hmm. Thanks. Please show us all the warnings you get.
Oleg.
next prev parent reply other threads:[~2016-09-13 15:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57D69CEC.5010103@kyup.com>
2016-09-12 13:01 ` BUG_ON in rcu_sync_func triggered Oleg Nesterov
2016-09-13 8:21 ` Nikolay Borisov
2016-09-13 13:18 ` Oleg Nesterov
2016-09-13 13:43 ` Oleg Nesterov
2016-09-13 14:35 ` Nikolay Borisov
2016-09-13 14:38 ` Nikolay Borisov
2016-09-13 14:39 ` Nikolay Borisov
2016-09-13 15:20 ` Oleg Nesterov [this message]
2016-09-14 6:30 ` Nikolay Borisov
2016-09-14 12:58 ` Oleg Nesterov
2016-09-23 13:35 ` Nikolay Borisov
2016-09-23 13:52 ` Oleg Nesterov
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=20160913152042.GA30160@redhat.com \
--to=oleg@redhat.com \
--cc=kernel@kyup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).