All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: netdev@oss.sgi.com, wensong@linux-vs.org, morpheus@theendless.org
Subject: Re: [2.6 PATCH] ipvs - avoid NULL ptr deref in __ip_vs_get_out_rt
Date: Tue, 11 Nov 2003 15:48:32 -0800	[thread overview]
Message-ID: <20031111154832.1017f57f.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0311120134540.2506-200000@u.domain.uli>

On Wed, 12 Nov 2003 01:46:43 +0200 (EET)
Julian Anastasov <ja@ssi.bg> wrote:

> 	The attached patch fixes the problem as reported from
> Kris (morpheus at theendless.org) under subject "linux-2.6.0-test9 and 
> IPVS (Kernel OOPS) with sync daemon started.". Kris reported that
> the fix works. It fixes a copy-and-paste bug which leads to dereferencing 
> a NULL ptr in __ip_vs_get_out_rt.

Applied, thanks Julian.

I assume 2.4.x does not need this fix.

  reply	other threads:[~2003-11-11 23:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11 23:46 [2.6 PATCH] ipvs - avoid NULL ptr deref in __ip_vs_get_out_rt Julian Anastasov
2003-11-11 23:48 ` David S. Miller [this message]
2003-11-12  0:01   ` Julian Anastasov

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=20031111154832.1017f57f.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ja@ssi.bg \
    --cc=morpheus@theendless.org \
    --cc=netdev@oss.sgi.com \
    --cc=wensong@linux-vs.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.