From: Greg KH <greg@kroah.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>,
bugme-daemon@bugzilla.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [Bug 6009] tcpdump causes kernel panic
Date: Thu, 9 Feb 2006 22:18:12 -0800 [thread overview]
Message-ID: <20060210061812.GB7939@kroah.com> (raw)
In-Reply-To: <1139162555.3017.11.camel@mulgrave.il.steeleye.com>
On Sun, Feb 05, 2006 at 12:02:35PM -0600, James Bottomley wrote:
> On Sat, 2006-02-04 at 16:51 -0800, Andrew Morton wrote:
> > in_interrupt() will return true in hard- or soft-irq context on all
> > architectures and all .configs - you can certainly use that.
> >
> > What we cannot use is in_atomic() to detect whether we're inside spinlock -
> > that only works if CONFIG_PREEMPT.
>
> OK, what do you think about this? It introduces an extra api to ensure
> user context. I suppose one think that could be done is to get the
> wrappers off a slab instead of using kmalloc, but that could be fixed up
> later.
This looks good to me, and odds are this function will come in handy for
other parts of the kernel.
thanks,
greg k-h
next prev parent reply other threads:[~2006-02-10 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602042315.k14NFwuS006966@fire-2.osdl.org>
2006-02-04 23:31 ` [Bug 6009] tcpdump causes kernel panic Andrew Morton
2006-02-05 0:18 ` James Bottomley
2006-02-05 0:51 ` Andrew Morton
2006-02-05 18:02 ` James Bottomley
2006-02-10 6:18 ` Greg KH [this message]
[not found] <200602050242.k152giEp014748@fire-2.osdl.org>
2006-02-05 5:04 ` Andrew Morton
[not found] <200602041838.k14Ic4Pi028741@fire-2.osdl.org>
2006-02-04 18:54 ` Andrew Morton
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=20060210061812.GB7939@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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