From: Chase Venters <chase.venters@clientec.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck@vds.kolivas.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: scsi cmd slab leak? (Was Re: [ck] Anyone been having OOM killer problems lately?)
Date: Thu, 19 Jan 2006 03:15:42 -0600 [thread overview]
Message-ID: <200601190316.05247.chase.venters@clientec.com> (raw)
In-Reply-To: <200601191849.45002.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 221 bytes --]
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
[-- Attachment #2: slabinfo --]
[-- Type: application/x-zerosize, Size: 19699 bytes --]
next parent reply other threads:[~2006-01-19 9:16 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 ` Chase Venters [this message]
2006-01-19 9:18 ` scsi cmd slab leak? (Was Re: [ck] Anyone been having OOM killer problems lately?) Con Kolivas
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=200601190316.05247.chase.venters@clientec.com \
--to=chase.venters@clientec.com \
--cc=ck@vds.kolivas.org \
--cc=kernel@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