mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Henry Qian" <henry@amperion.com>
To: "Manfred Spraul" <manfred@colorfullife.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: SLAB_LEVEL_MASK question
Date: Thu, 4 Sep 2003 16:19:36 -0400	[thread overview]
Message-ID: <C6D44AA99ECEB540A5498F15F92DA07DCF0DBA@amperion01> (raw)

The other flags are __GFP_WAIT, __GFP_HIGH, __GFP_IO, __GFP_HIGHIO, and
__GFP_FS (flags == 0x1f0).

So this must be something else's wrong.  I was using madwifi Atheros
driver.

Thank you very much,

Henry

-----Original Message-----
From: Manfred Spraul [mailto:manfred@colorfullife.com] 
Sent: Thursday, September 04, 2003 3:50 PM
To: Henry Qian
Cc: linux-kernel@vger.kernel.org
Subject: Re: SLAB_LEVEL_MASK question


Hi Henry,

>The kernel panics because in the flags variable, I have other flags
>(0x1f0) besides SLAB_ATOMIC.
>  
>
Which flags were set? __GFP_WAIT must not be set [i.e. will panic], the 
other combinations are invalid. The only legal values for the flags 
variable are 0 or SLAB_ATOMIC [aka GFP_ATOMIC, aka __GFP_HIGH].

>I modified it to:
>
>        if (in_interrupt() && (flags & SLAB_ATOMIC) != SLAB_ATOMIC)
>                BUG();
>
>It seems working fine.
>
>Is this good?
>  
>
No, it's wrong. Your driver will panic once in a while, especially under

memory intensive stress tests.

--
    Manfred


             reply	other threads:[~2003-09-04 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-04 20:19 Henry Qian [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-04 19:49 Manfred Spraul
2003-09-04 18:18 Henry Qian

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=C6D44AA99ECEB540A5498F15F92DA07DCF0DBA@amperion01 \
    --to=henry@amperion.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®