From: "Paweł Sikora" <pluto@pld-linux.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
arekm@pld-linux.org, baggins@pld-linux.org, herbert@13thfloor.at
Subject: Re: [2.6.38-3.x] [BUG] soft lockup - CPU#X stuck for 23s! (vfs, autofs, vserver)
Date: Mon, 24 Sep 2012 07:23:55 +0200 [thread overview]
Message-ID: <2819949.zde5vZ04eb@localhost> (raw)
In-Reply-To: <CA+55aFymD=QGptAxjSEWffDSA94dtAjPjy-ox76fYWgHn9m+kA@mail.gmail.com>
On Sunday 23 of September 2012 18:10:30 Linus Torvalds wrote:
> On Sat, Sep 22, 2012 at 11:09 PM, Paweł Sikora <pluto@pld-linux.org> wrote:
> >
> > br_read_lock(vfsmount_lock);
>
> The vfsmount_lock is a "local-global" lock, where a read-lock is
> rather cheap and takes just a per-cpu lock, but the downside is that a
> write-lock is *very* expensive, and can cause serious trouble.
>
> And the write lock is taken by the [un]mount() paths. Do *not* do
> crazy things. If you do some insane "unmount and remount autofs" on a
> 1s granularity, you're doing insane things.
>
> Why do you have that 1s timeout? Insane.
1s unmount timeout is *only* for fast bug reproduction (in few seconds after opteron startup)
and testing potential patches. normally with 60s timeout it happens in few minutes..hours
(depends on machine i/o+cpu load) and makes server unusable (permament soft-lockup).
can we redesign vserver's mnt_is_reachable() for better locking to avoid total soft-lockup?
BR,
Paweł.
ps).
i'm adding Herbert to CC.
next prev parent reply other threads:[~2012-09-24 5:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 6:09 [2.6.38-3.x] [BUG] soft lockup - CPU#X stuck for 23s! (vfs, autofs, vserver) Paweł Sikora
2012-09-23 6:09 ` Paweł Sikora
2012-09-24 1:10 ` Linus Torvalds
2012-09-24 5:23 ` Paweł Sikora [this message]
2012-09-24 11:23 ` Herbert Poetzl
2012-09-24 17:22 ` Linus Torvalds
2012-09-24 18:17 ` Eric W. Biederman
2012-09-24 18:17 ` Eric W. Biederman
2012-09-25 5:05 ` Herbert Poetzl
2012-11-15 18:48 ` Paweł Sikora
2012-11-15 19:22 ` Herbert Poetzl
2012-11-15 19:22 ` Herbert Poetzl
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=2819949.zde5vZ04eb@localhost \
--to=pluto@pld-linux.org \
--cc=arekm@pld-linux.org \
--cc=baggins@pld-linux.org \
--cc=herbert@13thfloor.at \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.