From: Johannes Berg <johannes@sipsolutions.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
linux-um@lists.infradead.org
Cc: richard@nod.at
Subject: Re: [PATCH v5] um: Enable preemption in UML
Date: Fri, 22 Sep 2023 11:10:32 +0200 [thread overview]
Message-ID: <efaa802bcd0369665b3dbc10030c9ca88aa2cb30.camel@sipsolutions.net> (raw)
In-Reply-To: <40babfb4-ed65-dd0e-23aa-abdfaa9c7149@cambridgegreys.com>
On Fri, 2023-09-22 at 10:06 +0100, Anton Ivanov wrote:
> On 22/09/2023 09:41, Johannes Berg wrote:
> > > Yes, but when does the fork actually happen?
> > >
> > Looking further at this, now I'm confused as to why it doesn't happen
> > _all_ the time.
> >
> > I think this has pretty much always been wrong, just now we actually
> > notice it?
> >
> > Basically, when we create a new thread (really just mm I think), we say
> > the first thing that has to run there is fork_handler(), which
> > initialises things the first time around. This calls force_flush_all()
> >
> > But of course it's called from __schedule(), which has
> > preemption/interrupts disabled. So you can't do mmap_read_lock()?
>
> Stupid question.
>
> If we have preemption and interrupts disabled and we are UP do we really need to lock it at this point?
Heh.
Functionally, I guess not. But lockdep gets really unhappy about stuff
in there:
=============================
WARNING: suspicious RCU usage
6.6.0-rc1 #159 Not tainted
-----------------------------
lib/maple_tree.c:840 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1
no locks held by startup.sh/282.
stack backtrace:
CPU: 0 PID: 282 Comm: startup.sh Not tainted 6.6.0-rc1 #159
Stack:
71a9bdd0 605001f3 00000000 6003cf40
606bd782 00000000 60b3e968 00000000
71a9be10 60526292 00000082 6051cb2a
Call Trace:
[<6051cb2a>] ? _printk+0x0/0x94
[<6002a5b4>] show_stack+0x13d/0x14c
[<605001f3>] ? dump_stack_print_info+0xde/0xed
[<6003cf40>] ? um_set_signals+0x0/0x3f
[<60526292>] dump_stack_lvl+0x62/0x96
[<6051cb2a>] ? _printk+0x0/0x94
[<605262e0>] dump_stack+0x1a/0x1c
[<6008865e>] lockdep_rcu_suspicious+0x10d/0x11c
[<6052721b>] ? debug_lockdep_rcu_enabled+0x0/0x3b
[<6052721b>] ? debug_lockdep_rcu_enabled+0x0/0x3b
[<605085cd>] mas_root+0x86/0x91
[<60508547>] ? mas_root+0x0/0x91
[<60508611>] mas_start+0x39/0x9c
[<60508875>] ? mas_state_walk+0x0/0x3e
[<6050888d>] mas_state_walk+0x18/0x3e
[<605088f1>] mas_walk+0x3e/0x96
[<60508a03>] mas_find_setup+0xba/0xcd
[<60509d49>] ? mas_find+0x0/0x4a
[<60509d71>] mas_find+0x28/0x4a
[<6002c92b>] force_flush_all+0x51/0x7c
[<6002926e>] fork_handler+0x14/0x96
johannes
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-09-22 9:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 6:52 [PATCH v5] um: Enable preemption in UML anton.ivanov
2023-09-22 7:27 ` Richard Weinberger
2023-09-22 7:29 ` Anton Ivanov
2023-09-22 7:30 ` Johannes Berg
2023-09-22 7:38 ` Anton Ivanov
2023-09-22 7:40 ` Johannes Berg
2023-09-22 8:01 ` Anton Ivanov
2023-09-22 8:13 ` Johannes Berg
2023-09-22 8:40 ` Anton Ivanov
2023-09-22 8:41 ` Johannes Berg
2023-09-22 8:43 ` Johannes Berg
2023-09-22 9:04 ` Johannes Berg
2023-09-22 9:12 ` Anton Ivanov
2023-09-22 9:06 ` Anton Ivanov
2023-09-22 9:10 ` Johannes Berg [this message]
2023-09-22 9:14 ` Johannes Berg
2023-09-22 9:19 ` Anton Ivanov
2023-09-22 9:51 ` Johannes Berg
2023-09-22 9:55 ` Johannes Berg
2023-09-22 10:55 ` Anton Ivanov
2023-09-22 11:17 ` Johannes Berg
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=efaa802bcd0369665b3dbc10030c9ca88aa2cb30.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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).