From: Adrian Bunk <bunk@stusta.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, aherrman@de.ibm.com
Subject: Re: [PATCH resubmit] do_mount: reduce stack consumption
Date: Sat, 5 Nov 2005 00:55:00 +0100 [thread overview]
Message-ID: <20051104235500.GE5368@stusta.de> (raw)
In-Reply-To: <20051104212742.GC9222@osiris.ibm.com>
On Fri, Nov 04, 2005 at 10:27:42PM +0100, Heiko Carstens wrote:
> > > See original stack back trace below and Andreas' patch and analysis
> > > here:
> > > http://www.ussg.iu.edu/hypermail/linux/kernel/0410.3/1844.html
>
> I probably should add that with "original" stack back trace a trace of
> a 2.6.10 kernel was meant, if that wasn't clear, but the DM code is
> still the same in 2.6.14.
>
> > > <4>Call Trace:
> ...
> > > <4> [<0000000010831380>] __map_bio+0x70/0x160 [dm_mod]
> > > <4> [<000000001083173e>] __split_bio+0x1e6/0x538 [dm_mod]
> > > <4> [<0000000010831ba8>] dm_request+0x118/0x25c [dm_mod]
> > > <4> [<0000000000241074>] generic_make_request+0xf0/0x21c
> > > <4> [<0000000010831380>] __map_bio+0x70/0x160 [dm_mod]
> > > <4> [<000000001083173e>] __split_bio+0x1e6/0x538 [dm_mod]
> > > <4> [<0000000010831ba8>] dm_request+0x118/0x25c [dm_mod]
> > > <4> [<0000000000241074>] generic_make_request+0xf0/0x21c
> > > <4> [<0000000010831380>] __map_bio+0x70/0x160 [dm_mod]
> > > <4> [<000000001083173e>] __split_bio+0x1e6/0x538 [dm_mod]
> > > <4> [<0000000010831ba8>] dm_request+0x118/0x25c [dm_mod]
> > > <4> [<0000000000241074>] generic_make_request+0xf0/0x21c
> ...
>
> This part of the call trace is actually good for >1500 bytes of stack
> usage and is what kills us and should be fixed.
> I'm surprised that there are no other bug reports regarding DM and
> stack overflow with 4k stacks.
>...
There were some reports of dm+xfs overflows with 4k stacks on i386.
The xfs side was sorted out, but I son't know the state of the dm part.
> Heiko
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-11-04 23:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 10:50 [PATCH resubmit] do_mount: reduce stack consumption Heiko Carstens
2005-11-04 11:48 ` Al Viro
2005-11-04 12:57 ` Heiko Carstens
2005-11-04 14:06 ` Al Viro
2005-11-04 22:03 ` Heiko Carstens
2005-11-04 16:48 ` Andrew Morton
2005-11-04 21:27 ` Heiko Carstens
2005-11-04 23:55 ` Adrian Bunk [this message]
2005-11-05 0:08 ` Andrew Morton
2005-11-05 0:08 ` Andrew Morton
2005-11-05 1:15 ` cplk
2005-11-05 1:37 ` Andrew Morton
2005-11-05 1:37 ` Andrew Morton
2005-11-05 5:37 ` Neil Brown
2005-11-05 5:37 ` Neil Brown
2005-11-07 0:16 ` Neil Brown
2005-11-07 0:16 ` [dm-devel] " Neil Brown
2005-11-07 16:15 ` Heiko Carstens
2005-11-07 22:12 ` Neil Brown
2005-11-07 23:37 ` Andrew Morton
2005-11-07 23:37 ` [dm-devel] " Andrew Morton
2005-11-08 0:32 ` Nick Piggin
2005-11-08 1:03 ` Neil Brown
2005-11-08 1:03 ` [dm-devel] " Neil Brown
2005-11-08 1:15 ` Andrew Morton
2005-11-08 1:15 ` [dm-devel] " Andrew Morton
2005-11-08 1:37 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2005-11-04 15:53 Andreas Herrmann
2005-11-04 17:42 ` Andrew Morton
2005-11-04 17:45 ` Arjan van de Ven
2005-11-04 18:37 ` Andrew Morton
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=20051104235500.GE5368@stusta.de \
--to=bunk@stusta.de \
--cc=aherrman@de.ibm.com \
--cc=akpm@osdl.org \
--cc=heiko.carstens@de.ibm.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 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.