From: Christoph Hellwig <hch@lst.de>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: poma <pomidorabelisima@gmail.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Vladimir Davydov <vdavydov@parallels.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux.com>,
Mailing-List fedora-kernel <kernel@lists.fedoraproject.org>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-scsi@vger.kernel.org
Subject: Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()
Date: Wed, 30 Jul 2014 19:59:58 +0200 [thread overview]
Message-ID: <20140730175958.GA30976@lst.de> (raw)
In-Reply-To: <53D929C3.3040709@cs.wisc.edu>
On Wed, Jul 30, 2014 at 12:22:11PM -0500, Mike Christie wrote:
> Some drivers like qla2xxx do not set proc_name. I think if 2 drivers
> like that are loaded then you will hit some other warns/bugs in the kmem
> cache setup code right?
Drivers have to opt into using their own caches by setting .cmd_size
in the host template. We could enforce they set ->proc_name for them,
but I'd rather keep the amount of sanity checks low unless there's a real
need.
next prev parent reply other threads:[~2014-07-30 18:00 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53C8DF7F.5060707@gmail.com>
2014-07-18 10:57 ` WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330() poma
2014-07-18 13:21 ` Vladimir Davydov
2014-07-18 13:21 ` Vladimir Davydov
2014-07-18 14:17 ` Christoph Hellwig
2014-07-18 14:17 ` Christoph Hellwig
[not found] ` <20140718141747.GA23272-jcswGhMUV9g@public.gmane.org>
2014-07-18 20:01 ` poma
2014-07-18 20:01 ` poma
2014-07-18 20:07 ` James Bottomley
2014-07-18 20:16 ` poma
[not found] ` <53C9808F.5040906-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-18 21:32 ` poma
2014-07-18 21:32 ` poma
2014-07-19 16:44 ` Christoph Hellwig
[not found] ` <20140719164454.GA24530-jcswGhMUV9g@public.gmane.org>
2014-07-21 9:39 ` poma
2014-07-21 9:39 ` poma
[not found] ` <53CCDFC3.5010802-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-21 14:58 ` Christoph Hellwig
2014-07-21 14:58 ` Christoph Hellwig
[not found] ` <20140721145817.GA15433-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-07-21 15:38 ` poma
2014-07-21 15:38 ` poma
2014-07-26 16:21 ` Christoph Hellwig
2014-07-26 16:21 ` Christoph Hellwig
2014-07-26 16:44 ` Martin K. Petersen
2014-07-27 8:09 ` Vladimir Davydov
2014-07-27 8:09 ` Vladimir Davydov
2014-07-28 7:49 ` James Bottomley
2014-07-29 12:26 ` Christoph Hellwig
[not found] ` <20140729122611.GA25980-jcswGhMUV9g@public.gmane.org>
2014-07-29 23:25 ` poma
2014-07-29 23:25 ` poma
2014-07-30 12:21 ` Josh Boyer
2014-07-30 12:21 ` Josh Boyer
[not found] ` <20140730122135.GE28613-dHPIJuKSOV01V+h/cAXI7w8O6CCKKCg3HZ5vskTnxNA@public.gmane.org>
2014-07-30 14:52 ` Christoph Hellwig
2014-07-30 14:52 ` Christoph Hellwig
2014-07-30 15:04 ` James Bottomley
2014-07-30 15:04 ` James Bottomley
2014-07-30 16:15 ` Christoph Hellwig
2014-07-30 17:22 ` Mike Christie
2014-07-30 17:59 ` Christoph Hellwig [this message]
[not found] ` <20140730175958.GA30976-jcswGhMUV9g@public.gmane.org>
2014-07-31 13:02 ` James Bottomley
2014-07-31 13:02 ` James Bottomley
2014-07-18 14:20 ` Christoph Lameter
2014-07-18 20:03 ` poma
2014-07-18 21:35 ` poma
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=20140730175958.GA30976@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=cl@linux.com \
--cc=kernel@lists.fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=pbonzini@redhat.com \
--cc=pomidorabelisima@gmail.com \
--cc=vdavydov@parallels.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 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.