All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] netlink bug?
Date: Wed, 25 Apr 2007 22:15:03 +0000	[thread overview]
Message-ID: <20070425221503.GA23236@kroah.com> (raw)
In-Reply-To: <462F68A8.5090803@kroon.co.za>

On Wed, Apr 25, 2007 at 04:41:44PM +0200, Jaco Kroon wrote:
>  Hi guys,
> 
>  I've got a piece of code that seems to reliably cause the kernel to panic, 
>  looks like a problem somewhere down the netlink core...
> 
>  I've been trying to use NETLINK_FIB_LOOKUP but so far the closest I've come 
>  to success was a kernel crash, a slightly stripped down version of the code 
>  that first crashed it attached.  If somebody else can confirm this it would 
>  be appreciated, also, any pointers on what I'm doing wrong that triggers the 
>  behaviour to begin with would be appreciated, thanks.
> 
>  I'm currently on kernel version 2.6.19.2, so this may have been fixed in the 
>  meantime.  Note that I don't need to run the code as root in order to 
>  trigger the crash.

Next time, if you find a kernel issue like this, could you just forward
this to the security@kernel.org mail alias?  This turned out to be a
real kernel issue, and now 2.6.20.8 is released with a fix for this
problem.

I still think there's a bug in your userspace program, but the kernel
shouldn't die anymore at least :)

thanks,

greg k-h
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors

  reply	other threads:[~2007-04-25 22:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25 14:41 [KJ] netlink bug? Jaco Kroon
2007-04-25 22:15 ` Greg KH [this message]
2007-04-25 22:25 ` Jaco Kroon

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=20070425221503.GA23236@kroah.com \
    --to=greg@kroah.com \
    --cc=kernel-janitors@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 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.