From: Jens Axboe <axboe@suse.de>
To: askernel2615@dsgml.com
Cc: Chase Venters <chase.venters@clientec.com>,
Mike Christie <michaelc@cs.wisc.edu>,
James Bottomley <James.Bottomley@SteelEye.com>,
Neil Brown <neilb@suse.de>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
akpm@osdl.org, a.titov@host.bg, jamie@audible.transient.net
Subject: Re: More information on scsi_cmd_cache leak... (bisect)
Date: Fri, 27 Jan 2006 21:06:35 +0100 [thread overview]
Message-ID: <20060127200635.GE9068@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0601271501300.8977@pureeloreel.qftzy.pbz>
On Fri, Jan 27 2006, askernel2615@dsgml.com wrote:
>
>
> On Fri, 27 Jan 2006, Chase Venters wrote:
>
> >On Fri, 27 Jan 2006, Jens Axboe wrote:
>
> >>The reports of leaks are only with > 2.6.15, not with 2.6.15.
>
> >Correction... my leak is with 2.6.15.
>
> Mine is also 2.6.15. Stock with debian patches.
>
> In fact I believe ALL the reports are from 2.6.15.
Hmm so does it happen in 2.6.16-rc1 or not? And try the suggestion I
made in the other, edit the sata driver for your device and set
ordered_flush to 0 instead of 1.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-27 20:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 10:09 More information on scsi_cmd_cache leak... (bisect) Chase Venters
2006-01-27 11:11 ` Neil Brown
2006-01-27 11:23 ` Jens Axboe
2006-01-27 11:28 ` Jens Axboe
2006-01-27 15:20 ` Chase Venters
2006-01-27 19:06 ` Mike Christie
2006-01-27 19:16 ` Jens Axboe
2006-01-27 19:20 ` James Bottomley
2006-01-27 19:29 ` Jens Axboe
2006-01-27 19:46 ` Mike Christie
2006-01-27 19:49 ` Jens Axboe
2006-01-27 19:53 ` Chase Venters
2006-01-27 20:00 ` Jens Axboe
2006-01-27 20:02 ` askernel2615
2006-01-27 20:06 ` Jens Axboe [this message]
2006-01-27 22:50 ` Tim Morley
2006-01-27 13:33 ` Alexey Dobriyan
2006-01-27 18:41 ` Ariel
2006-01-27 18:58 ` Chase Venters
2006-01-27 21:07 ` Neil Brown
2006-01-27 18:53 ` Ariel
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=20060127200635.GE9068@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=a.titov@host.bg \
--cc=akpm@osdl.org \
--cc=askernel2615@dsgml.com \
--cc=chase.venters@clientec.com \
--cc=jamie@audible.transient.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=neilb@suse.de \
/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.