mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: chatz@melbourne.sgi.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com, xfs-masters@oss.sgi.com, netdev@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: 2.6.19-rc6 : Spontaneous reboots, stack overflows - seems to implicate xfs, scsi, networking, SMP
Date: Tue, 21 Nov 2006 23:02:23 +0100	[thread overview]
Message-ID: <9a8748490611211402xdc2822fqbc95a77fe54d49b1@mail.gmail.com> (raw)
In-Reply-To: <45637566.5020802@melbourne.sgi.com>

On 21/11/06, David Chatterton <chatz@melbourne.sgi.com> wrote:
> Jesper,
>
> In the short term, the best workaround is to use 8K stacks.

Yeah, that's what I'm currently doing and the box seems more stable
(at least it has not crashed yet, but with 4K stacks it usually would
have by now).

> We do not see stack
> overflow problems with NFS + XFS + volume managers + disk devices.
>
Could the size of my devices be part of the cause? some of the logical
volumes I have mounted are multiple TB in size?


> Audits have been done in the past and will again be done in the future to try to
> identify areas where XFS could use less stack space by reducing/avoid large
> local variables. Reducing the code path is far more difficult.
>
I realize that fixing the problem may be difficult. I just wanted to
make sure that people were informed that there is an actual problem
and provide as much info as possible so that perhaps in the future it
can be fixed... :)
I'm reading through the XFS code myself at the moment and I'll be sure
to submit patches if I spot something that could help reduce stack
usage.


> There is active discussion about reducing inlining:
> http://bugzilla.kernel.org/show_bug.cgi?id=7364
>

Thanks, I'll check that out.


> I can't speak for the scsi stack usage.
>
> Thanks for traces, I've captured this information.
>
You are welcome. If you want/need more traces then I've got ~2.1G
worth of traces that you can have :)


Thank you for your reply.


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2006-11-21 22:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21  9:27 Jesper Juhl
2006-11-21 21:53 ` David Chatterton
2006-11-21 22:02   ` Jesper Juhl [this message]
2006-11-21 23:31     ` David Chinner
2006-11-21 23:51       ` Jesper Juhl
2006-11-22 12:58         ` Jesper Juhl
2006-11-22 20:01           ` Stephen Hemminger
2006-11-23 10:27             ` Jesper Juhl
2006-11-23  1:18           ` David Chinner
2006-11-23  4:10             ` David Miller
2006-11-23  4:35               ` Al Viro
2006-11-23  6:47                 ` Matthew Wilcox
2006-11-23  8:12                 ` Arjan van de Ven
2006-11-23 22:08                   ` [xfs-masters] " Nathan Scott
2006-11-26 14:31                   ` Eric Sandeen
2006-11-23  7:08               ` David Chinner
2006-11-23 13:16                 ` Ingo Oeser
2006-11-23 18:37                   ` Arjan van de Ven
2006-11-23 19:54                     ` David Miller
2006-11-24  0:55                     ` David Chinner
2006-11-24  1:08                       ` Jesper Juhl
2006-11-24  2:05                         ` David Chinner
2006-11-24  7:52                       ` Arjan van de Ven
2006-11-23 19:42                 ` David Miller
2006-11-29  1:56             ` David Chinner

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=9a8748490611211402xdc2822fqbc95a77fe54d49b1@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=chatz@melbourne.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xfs-masters@oss.sgi.com \
    --cc=xfs@oss.sgi.com \
    /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

all inboxes | Powered by JetHome®