From: "David S. Miller" <davem@redhat.com>
To: Krishna Kumar <krkumar@us.ibm.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH 3/5] xfrm_lookup bugs
Date: Tue, 13 Jan 2004 23:23:35 -0800 [thread overview]
Message-ID: <20040113232335.2236706f.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401131322440.25742-100000@linux-udp14999547uds>
On Tue, 13 Jan 2004 13:23:35 -0800 (PST)
Krishna Kumar <krkumar@us.ibm.com> wrote:
> In xfrm_lookup, a couple of bugs :
> - the found or allocated xfrm_states are not passed correctly to
> xfrm_bundle_create (and to the subsequent frees in case of create
> failing) if the first xfrm_tmpl_resolve failed and the second one
> succeeded.
> - error handling is wrong.
Looks fine, patch applied thanks.
next prev parent reply other threads:[~2004-01-14 7:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 18:33 [PATCH] Bugs in xfrm Krishna Kumar
2004-01-10 20:11 ` David S. Miller
2004-01-13 21:21 ` [PATCH 1/5] ipcomp_tunnel_create doesn't set tunnel state Krishna Kumar
2004-01-13 21:22 ` [PATCH 2/5] Bad dereference of xfrm_state in pf_key Krishna Kumar
2004-01-14 7:21 ` David S. Miller
2004-01-13 21:23 ` [PATCH 3/5] xfrm_lookup bugs Krishna Kumar
2004-01-14 7:23 ` David S. Miller [this message]
2004-01-13 21:24 ` [PATCH 4/5] xfrm_state_construct doesn't set tunnel state Krishna Kumar
2004-01-14 7:25 ` David S. Miller
2004-01-13 21:26 ` [PATCH 5/5] schedule() bug in xfrm_lookup() Krishna Kumar
2004-01-14 7:27 ` David S. Miller
2004-01-14 7:20 ` [PATCH 1/5] ipcomp_tunnel_create doesn't set tunnel state David S. Miller
2004-03-09 21:36 ` [PATCH] Trivial kmalloc failure checks Krishna Kumar
2004-03-09 23:24 ` 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=20040113232335.2236706f.davem@redhat.com \
--to=davem@redhat.com \
--cc=krkumar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).