From: Patrick McHardy <kaber@trash.net>
To: Bernhard Walle <bwalle@suse.de>
Cc: Miika Komu <miika@iki.fi>, netdev@vger.kernel.org
Subject: Re: [PATCH] Fix oops in xfrm4_dst_destroy()
Date: Mon, 26 Feb 2007 01:24:37 +0100 [thread overview]
Message-ID: <45E228C5.3060108@trash.net> (raw)
In-Reply-To: <20070225204315.GB31715@strauss.suse.de>
Bernhard Walle wrote:
> With 2.6.21-rc1, I get an oops when running 'ifdown eth0' and an IPsec
> connection is active. If I shut down the connection before running 'ifdown
> eth0', then there's no problem. The critical operation of this script is to
> kill dhcpd.
>
> The problem is probably caused by commit with git identifier
> 4337226228e1cfc1d70ee975789c6bd070fb597c (Linus tree) "[IPSEC]: IPv4 over IPv6
> IPsec tunnel".
>
> This patch fixes that oops. I don't know the network code of the Linux kernel
> in deep, so if that fix is wrong, please change it. But please fix the oops. :)
Looks good, when the xfrm_dst is freed in __xfrm4_bundle_create
after a failed call to xfrm_dst_lookup the xfrm pointer is not
set, and this is also expected by xfrm_dst_destroy.
Acked-by: Patrick McHardy <kaber@trash.net>
> ---
> net/ipv4/xfrm4_policy.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6.21-rc1/net/ipv4/xfrm4_policy.c
> ===================================================================
> --- linux-2.6.21-rc1.orig/net/ipv4/xfrm4_policy.c
> +++ linux-2.6.21-rc1/net/ipv4/xfrm4_policy.c
> @@ -291,7 +291,7 @@ static void xfrm4_dst_destroy(struct dst
>
> if (likely(xdst->u.rt.idev))
> in_dev_put(xdst->u.rt.idev);
> - if (dst->xfrm->props.family == AF_INET && likely(xdst->u.rt.peer))
> + if (dst->xfrm && dst->xfrm->props.family == AF_INET && likely(xdst->u.rt.peer))
> inet_putpeer(xdst->u.rt.peer);
> xfrm_dst_destroy(xdst);
> }
next prev parent reply other threads:[~2007-02-26 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 20:43 [PATCH] Fix oops in xfrm4_dst_destroy() Bernhard Walle
2007-02-26 0:24 ` Patrick McHardy [this message]
2007-02-26 20:10 ` David 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=45E228C5.3060108@trash.net \
--to=kaber@trash.net \
--cc=bwalle@suse.de \
--cc=miika@iki.fi \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).