netdev - Re: An ioctl to delete an ipv6 tunnel leads to a kernel panic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Feb 2008 21:49:46 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	protasnb@...il.com
Cc:	netdev@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: An ioctl to delete an ipv6 tunnel leads to a kernel panic

From: "Natalie Protasevich" <protasnb@...il.com>
Date: Mon, 11 Feb 2008 12:49:12 -0800

> Possible reason for this failure was identified and tested by the
> submitter and several other reporters that ran into the same problem.
> Can the patch be reviewed and pushed upstream if accepted (if the
> problem hasn't been addressed already)?

There are a lot of bogus patches in there, using funny
long variable names, and mainly they were meant for testing
and verification of the problem.

I see no real serious patch submissions in that bug and furthermore
the patch, if ready, should be submitted formally here to netdev not
rot in bugzilla.

Finally, what appears to be the proposal cannot be correct.  If the
fib6_add_rt2node() finds that the new route is a duplicate, we should
disconnect it from the fn->leaf and do a dst_release().  The bug
appears to be rather that we leave the route attached to the fn, not
that we drop the refrence to it.

Thank you.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html