netdev - Re: [PATCH V3 net-next 1/3] ipv6: add the IPV6_FL_F_REFLECT flag to IPV6_FL_A

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] [day] [month] [year] [list]

Message-ID: <52D949DC.40407@enst-bretagne.fr>
Date:	Fri, 17 Jan 2014 16:18:52 +0100
From:	Florent Fourcot <florent.fourcot@...t-bretagne.fr>
To:	netdev@...r.kernel.org,
	Hannes Frederic Sowa <hannes@...essinduktion.org>
Subject: Re: [PATCH V3 net-next 1/3] ipv6: add the IPV6_FL_F_REFLECT flag
 to IPV6_FL_A_GET


>>
>> I am not sure here, do you write the flow_label on the listening socket?
>>
> 
> Hum, yes. You are right, this is bad.
> 
> One alternative is not so simple. Perhaps could we store the flowlabel
> in inet_request_sock? It will be available in the tcp_v6_send_synack
> function, even in case of retransmission.


Ok, it is possible to use ireq->pktopts, without adding any memory
overhead for other users. I will send a V4.

Thanks Hannes,

Florent.
--
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