netdev - Re: [PATCH net-next v4 3/3] net: ipv6: Use ip6_datagram_send

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]

Message-ID: <CAKD1Yr0+1ox+Sq0Ze9oPkzE_2SvqH6wY7AgGRFFm9Ta15NRnKw@mail.gmail.com>
Date:	Fri, 25 Apr 2014 01:06:04 +0900
From:	Lorenzo Colitti <lorenzo@...gle.com>
To:	Lorenzo Colitti <lorenzo@...gle.com>,
	Florent Fourcot <florent.fourcot@...t-bretagne.fr>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>,
	David Miller <davem@...emloft.net>,
	Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: [PATCH net-next v4 3/3] net: ipv6: Use ip6_datagram_send_common
 in ping.

On Fri, Apr 25, 2014 at 12:35 AM, Lorenzo Colitti <lorenzo@...gle.com> wrote:
> I suppose that since ping_v4_push_pending_frames gets called with the
> socket locked, we might be able to get away with setting
> sk->sk_protocol just before ping_v4_push_pending_frames and restoring
> it afterwards. But that feels hacky and I don't know what else it
> could break.

FWIW, here's what it looks like: http://patchwork.ozlabs.org/patch/342428/
--
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