From: Dominique Martinet <dominique.martinet@cea.fr>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
V9FS Developers <v9fs-developer@lists.sourceforge.net>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: [V9fs-developer] Hang triggered by udev coldplug, looks like a race
Date: Mon, 7 Dec 2015 23:46:43 +0100 [thread overview]
Message-ID: <20151207224643.GA10531@nautica> (raw)
In-Reply-To: <CALCETrX8ukASsKfTgmN6SzDVG5L61GrSc6i26SvKu1OQt7_xTA@mail.gmail.com>
Andy Lutomirski wrote on Mon, Dec 07, 2015:
> On Thu, Dec 3, 2015 at 9:52 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> > Sometimes udevadm trigger --action=add hangs the system, and the splat
> > below happens. This seems to be timing dependent, and I haven't been
> > able to trigger it yet with lockdep enabled, sadly.
> >
> > Any ideas? I not, I'll try to instrument it better tomorrow.
>
> More details: this is caused by a storm of /sbin/hotplug UMH calls
> (yes, misconfigured kernel, but still). /sbin is a symlink to
> /usr/sbin, /usr/sbin/hotplug doesn't exist, and all of the above is on
> rootfs, which is 9p over virtio.
>
> Pointing uevent_helper at /usr/sbin/hotplug (which still doesn't
> exist) seems to work around it.
Can you reproduce it on a booted system with something like
`seq 1 1000000 | xargs -P 1024 -I{} cat /sbin/foo >&/dev/null` ?
(trying execs might be closer to your workload, not sure how much this
or using umh might change)
Also, what qemu version please just to try to match your environment ?
--
Dominique Martinet
next prev parent reply other threads:[~2015-12-07 22:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 5:52 Hang triggered by udev coldplug, looks like a race Andy Lutomirski
2015-12-07 19:18 ` Andy Lutomirski
2015-12-07 22:46 ` Dominique Martinet [this message]
2015-12-08 1:59 ` [V9fs-developer] " Andy Lutomirski
2015-12-08 2:33 ` Al Viro
2015-12-08 22:49 ` Andy Lutomirski
2015-12-09 6:23 ` Dominique Martinet
2015-12-09 6:41 ` Dominique Martinet
2015-12-09 6:45 ` Al Viro
2015-12-17 21:06 ` Andy Lutomirski
2015-12-24 10:51 ` Dominique Martinet
2015-12-30 6:43 ` Andy Lutomirski
2016-01-04 15:59 ` Peter Zijlstra
2016-01-04 16:09 ` Dominique Martinet
2016-01-04 19:07 ` Andy Lutomirski
2016-01-04 19:27 ` Peter Zijlstra
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=20151207224643.GA10531@nautica \
--to=dominique.martinet@cea.fr \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=v9fs-developer@lists.sourceforge.net \
/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).