From: Oleg Nesterov <oleg@redhat.com>
To: Nikolay Borisov <kernel@kyup.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: BUG_ON in rcu_sync_func triggered
Date: Fri, 23 Sep 2016 15:52:50 +0200 [thread overview]
Message-ID: <20160923135250.GA28734@redhat.com> (raw)
In-Reply-To: <CAJFSNy4EZzL7+aWC8xD63rTgcQ3OaBokNB_scpzRDRA53sukEA@mail.gmail.com>
On 09/23, Nikolay Borisov wrote:
>
> > --- a/fs/super.c
> > +++ b/fs/super.c
> > @@ -1344,7 +1344,9 @@ int thaw_super(struct super_block *sb)
> > int error;
> >
> > down_write(&sb->s_umount);
> > - if (sb->s_writers.frozen == SB_UNFROZEN) {
> > + if (sb->s_writers.frozen != SB_FREEZE_COMPLETE) {
> > + if (sb->s_writers.frozen != SB_UNFROZEN)
> > + pr_crit("THAW: hit the race: %d\n", sb->s_writers.frozen);
> > up_write(&sb->s_umount);
> > return -EINVAL;
> > }
> >
>
> I was away on holiday so that's why I was silent. However, with this
> patch applied I couldn't reproduce the issue nor the pr_crit
> triggered.
Great, thanks a lot.
> Have you had any moments of epiphany re. this issue?
Well, after I failed to find any problem in rcu/sync.c I started to
look at the callers and found this race.
> Should
> some FS people be involved in the discussion?
Sure. I'll send the patch with CC's. Probably next week, I am too
busy right now.
Thanks Nikolay,
Oleg.
prev parent reply other threads:[~2016-09-23 13:53 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
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 [this message]
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=20160923135250.GA28734@redhat.com \
--to=oleg@redhat.com \
--cc=kernel@kyup.com \
--cc=linux-kernel@vger.kernel.org \
/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).