public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Denys Fedoryschenko <denys@visp.net.lb>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unable to handle kernel NULL pointer / tty / 2.6.31-rc7
Date: Tue, 25 Aug 2009 14:19:44 -0700	[thread overview]
Message-ID: <20090825211944.GA21257@suse.de> (raw)
In-Reply-To: <200908252237.54324.denys@visp.net.lb>

On Tue, Aug 25, 2009 at 10:37:54PM +0300, Denys Fedoryschenko wrote:
> Kernel 2.6.31-rc7
> x86 , 32-bit
> gcc 4.4.1
> 
> 
> Happened on heavy network load, i don't know if it is related.
> 
> Here is part of remote syslog, notice failed dropbear ssh authentication.
> I guess if it is not fixed - it is critical to upcoming release, seems bug 
> triggered by ssh worm.
> 
> Aug 25 22:34:35 10.22.24.2 login[2099]: pam_radius_auth: DEBUG: 
> getservbyname(radius, udp) returned -1209037784.
> Aug 25 22:34:36 10.22.24.2 login[2099]: pam_unix(login:auth): authentication 
> failure; logname= uid=0 euid=0 tty=pts/0 ruser= rhost=  user=root
> Aug 25 22:34:37 10.22.24.2 ripd[1862]: rip_read: cannot find interface for 
> packet from 80.83.24.49 port 520
> Aug 25 22:34:41 10.22.24.2 ripd[1862]: Neighbor 10.22.22.2 doesnt have 
> connected interface!
> Aug 25 22:34:46 10.22.24.2 kernel: [22630.973706] BUG: unable to handle kernel 
> NULL pointer dereference at (null)
> Aug 25 22:34:46 10.22.24.2 kernel: [22630.973807] IP: [<c0251814>] 
> n_tty_read+0x3c6/0x5ad
> 
> Full BUG message
> 
> 
>  [22630.973706] BUG: unable to handle kernel NULL pointer dereference at 
> (null)

Can you try this on Linus's latest tree, he has just fixed a bug in this
area.

thanks,

greg k-h

      reply	other threads:[~2009-08-25 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 19:37 unable to handle kernel NULL pointer / tty / 2.6.31-rc7 Denys Fedoryschenko
2009-08-25 21:19 ` Greg KH [this message]

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=20090825211944.GA21257@suse.de \
    --to=gregkh@suse.de \
    --cc=denys@visp.net.lb \
    --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