All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Krishna Kumar <krkumar@us.ibm.com>
Cc: netdev@oss.sgi.com, krkumar@us.ibm.com, kumarkr@us.ibm.com
Subject: Re: [PATCH] Bugs in xfrm
Date: Fri, 9 Jan 2004 20:48:08 -0800	[thread overview]
Message-ID: <20040109204808.3db77be6.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401091339170.10121-100000@linux-udp14999547uds>

On Fri, 9 Jan 2004 17:40:03 -0800 (PST)
Krishna Kumar <krkumar@us.ibm.com> wrote:

> These changes compile cleanly, but I couldn't test since these are
> corner cases. Please let me know if this can be applied. I am sending
> as one patch file for now instead of multiple files as they all small.

Maybe you should actually try to test these changes before I think
about applying them, for example:

> +void dst_bundle_free(struct dst_entry *dst)
> +{
> +	struct dst_entry *next;
> +
> +	while (dst) {
> +		next = dst->child;
> +		dst_free(dst);
> +	}
> +}

Explain to me how that won't loop forever if given a non-NULL dst?

Next, this dst_bundle_free() thing is totally not needed as far as I can
tell.  When dst_free() is made, the top-level of the bundle's dst gets added
to the garbage collection list, the garbage collection properly walks the
children to process the whole bundle.

Please redo this patch and please test it this time :)

  reply	other threads:[~2004-01-10  4:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06 19:58 [PATCH] panic during unregister_netdevice() Krishna Kumar
2003-11-06 19:59 ` David S. Miller
2003-11-06 21:07   ` Krishna Kumar
2003-11-06 21:14     ` David S. Miller
2003-11-07 19:01   ` [PATCH] Hang in downing interface with IPv6 PRIVACY Krishna Kumar
2003-11-09  6:30     ` David S. Miller
2004-01-10  1:40       ` [PATCH] Bugs in xfrm Krishna Kumar
2004-01-10  4:48         ` David S. Miller [this message]
2004-01-10 18:33 Krishna Kumar
2004-01-10 20:11 ` David S. Miller

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=20040109204808.3db77be6.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=krkumar@us.ibm.com \
    --cc=kumarkr@us.ibm.com \
    --cc=netdev@oss.sgi.com \
    /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.