From: romieu@fr.zoreil.com
To: Bart De Schuymer <bdschuym@pandora.be>
Cc: linux-kernel@vger.kernel.org, buytenh@gnu.org
Subject: Re: oops when adding bridge interface, using v2.5.45
Date: Mon, 11 Nov 2002 00:08:56 +0100 [thread overview]
Message-ID: <20021111000856.A8050@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <200211110052.29495.bdschuym@pandora.be>; from bdschuym@pandora.be on Mon, Nov 11, 2002 at 12:52:29AM +0100
Bart De Schuymer <bdschuym@pandora.be> :
[...]
> net/bridge/br_if.c::new_nbp() does
> p = kmalloc(sizeof(*p), GFP_KERNEL);
> which triggers the oops through mm/slab.c::kmem_flagcheck()
> I don't know what is wrong (I have no such problems with 2.4).
>
> The trace is below:
[sleeping function called with lock held]
[net/bridge/br_if.c:236]
write_lock_bh(&br->lock);
if ((p = new_nbp(br, dev)) == NULL) {
write_unlock_bh(&br->lock);
Following patch should fix it. It looks the same in 2.5.46.
--- net/bridge/br_if.c Sun Nov 10 23:57:28 2002
+++ net/bridge/br_if.c Sun Nov 10 23:57:57 2002
@@ -143,7 +143,7 @@ static struct net_bridge_port *new_nbp(s
int i;
struct net_bridge_port *p;
- p = kmalloc(sizeof(*p), GFP_KERNEL);
+ p = kmalloc(sizeof(*p), GFP_ATOMIC);
if (p == NULL)
return p;
--
Ueimor
next prev parent reply other threads:[~2002-11-10 23:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 22:19 [RFC] devfs API Alexander Viro
2002-11-10 23:52 ` oops when adding bridge interface, using v2.5.45 Bart De Schuymer
2002-11-10 23:08 ` romieu [this message]
2002-11-11 0:49 ` Bart De Schuymer
2002-11-12 1:32 ` [RFC] devfs API Ryan Anderson
2002-11-12 1:49 ` Alexander Viro
2002-11-12 8:04 ` Theodore Ts'o
2002-11-12 8:44 ` Rudmer van Dijk
2002-11-12 9:50 ` Miles Bader
2002-11-12 10:57 ` Helge Hafting
2002-11-12 9:43 ` Alexander Viro
2002-11-12 10:47 ` Helge Hafting
2002-11-12 21:57 ` Jon Portnoy
2002-11-13 15:15 ` Denis Vlasenko
2002-11-12 1:50 ` Robert Love
2002-11-12 11:44 ` William Lee Irwin III
2002-11-14 17:51 ` Richard Gooch
2002-11-14 18:04 ` Alexander Viro
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=20021111000856.A8050@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=bdschuym@pandora.be \
--cc=buytenh@gnu.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
Powered by JetHome