From: Con Kolivas <kernel@kolivas.org>
To: Chase Venters <chase.venters@clientec.com>
Cc: ck@vds.kolivas.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: scsi cmd slab leak? (Was Re: [ck] Anyone been having OOM killer problems lately?)
Date: Thu, 19 Jan 2006 20:18:49 +1100 [thread overview]
Message-ID: <200601192018.51972.kernel@kolivas.org> (raw)
In-Reply-To: <200601190316.05247.chase.venters@clientec.com>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On Thursday 19 January 2006 20:15, Chase Venters wrote:
> On Thursday 19 January 2006 01:49, Con Kolivas wrote:
> > > Do I have something madly leaking in my kernel?
> >
> > Yes! post /proc/slabinfo
>
> (attached). Looks like quite a few scsi commands! Next steps?
>
> > Con
>
> Thanks!
> Chase
Inded it does
scsi_cmd_cache 1547440 1547440 384 10 1 : tunables 54 27 8 :
slabdata 154744 154744 0
This looks suspiciously large. To be absolutely certain, though, you have to
reproduce the problem with a vanilla kernel, and no binary drivers anywhere.
My patches don't touch the scsi code directly, but the only way to be certain
is to use vanilla.
Cheers,
Con
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-19 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200601181951.16708.chase.venters@clientec.com>
[not found] ` <200601190113.32153.chase.venters@clientec.com>
[not found] ` <200601191849.45002.kernel@kolivas.org>
2006-01-19 9:15 ` scsi cmd slab leak? (Was Re: [ck] Anyone been having OOM killer problems lately?) Chase Venters
2006-01-19 9:18 ` Con Kolivas [this message]
2006-01-19 9:34 ` Chase Venters
2006-01-19 18:13 ` scientica (GMail)
2006-01-19 18:22 ` Chase Venters
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=200601192018.51972.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=chase.venters@clientec.com \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox