From: "Jeff Merkey" <jmerkey@timpanogas.org>
To: "Jeff Merkey" <jmerkey@timpanogas.org>,
<jmerkey@vger.timpanogas.org>,
"David S. Miller" <davem@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [VM/MEMORY-SICKNESS] 2.4.15-pre7 kmem_cache_create invalid opcode
Date: Tue, 20 Nov 2001 23:59:43 -0700 [thread overview]
Message-ID: <002501c1725a$19022a80$f5976dcf@nwfs> (raw)
> > You are really a fucking pain in the ass to help Jeff.
>
> Dave, I went and looked at this stuff. I have been running this code for
> over a year on 2.4 and I AM NOT CREATING A SLAB CACHE TWICE!!!!
> I am building an NWFS module external of the kernel tree, and unless make
> dep
> has been run, the default behavior of the includes causes me to drop into
> the
> BUG() trap.
This is a bug in how these includes are structured. It may be ok to leave
the damn
thing the way it is, but warn folks who build custom drivers (like the SCI
drivers I
maintain for Dolphin, NWFS, etc.) that their f_cking code will be broken and
generate these garbage errors if they have not run make dep against the tree
they
try to build against.
I would not have expected you or most LKML folks to have seen this, since
you live
in a world where everything is in the kernel tree. I am telling you there
is a problem there,
and it can bite. After I build this module (since the generated code thatr
ends up in
the external module is crap) it will routinely crash over and over gain
until it gets rebuilt
against a kernel that has had make dep (and make bzImage) run against it.
Jeff
>
> Jeff
>
>
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
next reply other threads:[~2001-11-21 7:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 6:59 Jeff Merkey [this message]
[not found] <davem@redhat.com>
2001-11-21 7:16 ` [VM/MEMORY-SICKNESS] 2.4.15-pre7 kmem_cache_create invalid opcode Jeff V. Merkey
2001-11-21 6:22 ` David S. Miller
2001-11-21 7:33 ` Jeff V. Merkey
2001-11-21 6:47 ` Kai Henningsen
2001-11-21 18:28 ` Jeff Merkey
2001-11-21 6:47 ` David S. Miller
2001-11-21 6:54 ` Jeff Merkey
2001-11-21 6:56 ` David S. Miller
2001-11-21 7:03 ` Jeff Merkey
2001-11-21 7:09 ` David S. Miller
2001-11-21 7:14 ` Jeff Merkey
2001-11-21 7:28 ` Stuart Young
2001-11-21 7:49 ` arjan
2001-11-21 18:31 ` Jeff Merkey
2001-11-21 19:06 ` Doug Ledford
2001-11-21 19:51 ` Jeff Merkey
2001-11-21 19:58 ` J Sloan
2001-11-21 20:38 ` Doug Ledford
2001-11-21 21:17 ` Jeff Merkey
2001-11-21 19:16 ` Arjan van de Ven
2001-11-21 19:53 ` Jeff Merkey
2001-11-21 20:36 ` Doug Ledford
2001-11-21 21:16 ` Jeff Merkey
2001-11-21 21:28 ` Robert Love
2001-11-21 6:54 ` Chris Abbey
2001-11-21 7:05 ` Jeff Merkey
2001-11-21 8:49 ` Alan Cox
2001-11-21 18:28 ` Jeff Merkey
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='002501c1725a$19022a80$f5976dcf@nwfs' \
--to=jmerkey@timpanogas.org \
--cc=davem@redhat.com \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@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