mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve Whitehouse <steve@gw.chygwyn.com>
To: davem@redhat.com (David S. Miller)
Cc: engler@csl.Stanford.EDU (Dawson Engler),
	linux-kernel@vger.kernel.org, mc@cs.Stanford.EDU, philb@gnu.org
Subject: Re: [CHECKER] 84 bugs in 2.4.4/2.4.4-ac8 where NULL pointers are deref'd
Date: Tue, 29 May 2001 23:56:10 +0100 (BST)	[thread overview]
Message-ID: <200105292256.XAA16415@gw.chygwyn.com> (raw)
In-Reply-To: <15124.9340.77101.588276@pizda.ninka.net> from "David S. Miller" at May 29, 2001 03:36:44 PM

Hi,

> 
> 
> [ Steve: Just skim down to the decnet bug, you should have a look
>          at it.
> 
[various bits deleted]

Thanks for pointing this out. At first glance the problem is not where the
error says that it is since it should be impossible to get here with a NULL
neighbour cache entry (well we shouldn't be creating an output route without
a next hop :-)

I've got some other little DECnet fixes to forward shortly, but I'm probably
not going to get a chance to do so before the end of the week now so I'll
look at this properly and send fixes then,

Steve.

[DECnet bug report reproduced here for context]
>  > ---------------------------------------------------------
>  > [BUG] contradicts
>  > /u2/engler/mc/oses/linux/2.4.4/net/decnet/dn_route.c:808:dn_route_output_slow: ERROR:INTERNAL_NULL:798:808: [type=set] (set at line 798) Dereferencing NULL ptr "neigh" illegally! [val=1000]
>  > 	
>  > 	rt->key.saddr  = src;
>  > 	rt->rt_saddr   = src;
>  > 	rt->key.daddr  = dst;
>  > 	rt->rt_daddr   = dst;
>  > Start --->
>  > 	rt->key.oif    = neigh ? neigh->dev->ifindex : -1;
>  > 	rt->key.iif    = 0;
>  > 	rt->key.fwmark = 0;
>  > 
>  > 	rt->u.dst.neighbour = neigh;
>  > 	rt->u.dst.dev = neigh ? neigh->dev : NULL;
>  > 	rt->u.dst.lastuse = jiffies;
>  > 	rt->u.dst.output = dn_output;
>  > 	rt->u.dst.input  = dn_rt_bug;
>  > 
>  > Error --->
>  > 	if (dn_dev_islocal(neigh->dev, rt->rt_daddr))
>  > 		rt->u.dst.input = dn_nsp_rx;
>  > 
>  > 	hash = dn_hash(rt->key.saddr, rt->key.daddr);
> 
> Yeah, this one is wrong, I'll leave this to Steve Whitehouse though,
> the DecNET maintainer.
> 

  reply	other threads:[~2001-05-29 22:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29 21:49 Dawson Engler
2001-05-29 22:36 ` Alexander Viro
2001-05-29 22:36 ` David S. Miller
2001-05-29 22:56   ` Steve Whitehouse [this message]
2001-05-29 23:09   ` Dawson Engler
2001-05-30  5:17 ` Andreas Dilger
2001-05-30  5:45   ` Alexander Viro
2001-05-30  6:49     ` Andreas Dilger
2001-05-30  6:58       ` 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=200105292256.XAA16415@gw.chygwyn.com \
    --to=steve@gw.chygwyn.com \
    --cc=Steve@ChyGwyn.com \
    --cc=davem@redhat.com \
    --cc=engler@csl.Stanford.EDU \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mc@cs.Stanford.EDU \
    --cc=philb@gnu.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

all inboxes | Powered by JetHome®