From: David Miller <davem@davemloft.net>
To: florent.fourcot@enst-bretagne.fr
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/5] ipv6: add flowinfo for tcp6 pkt_options for all cases
Date: Mon, 09 Dec 2013 21:04:07 -0500 (EST) [thread overview]
Message-ID: <20131209.210407.175864636691434095.davem@davemloft.net> (raw)
In-Reply-To: <1386514021-11646-1-git-send-email-florent.fourcot@enst-bretagne.fr>
From: Florent Fourcot <florent.fourcot@enst-bretagne.fr>
Date: Sun, 8 Dec 2013 15:46:57 +0100
> The current implementation of IPV6_FLOWINFO only gives a
> result if pktoptions is available (thanks to the
> ip6_datagram_recv_ctl function).
> It gives inconsistent results to user space, sometimes
> there is a result for getsockopt(IPV6_FLOWINFO), sometimes
> not.
>
> This patch add rcv_flowinfo to store it, and return it to
> the userspace in the same way than other pkt_options.
>
> Signed-off-by: Florent Fourcot <florent.fourcot@enst-bretagne.fr>
Applied.
prev parent reply other threads:[~2013-12-10 2:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 14:46 [PATCH net-next 1/5] ipv6: add flowinfo for tcp6 pkt_options for all cases Florent Fourcot
2013-12-08 14:46 ` [PATCH net-next 2/5] ipv6: move IPV6_TCLASS_MASK definition in ipv6.h Florent Fourcot
2013-12-09 23:41 ` Hannes Frederic Sowa
2013-12-10 2:04 ` David Miller
2013-12-08 14:46 ` [PATCH net-next 3/5] ipv6: remove rcv_tclass of ipv6_pinfo Florent Fourcot
2013-12-09 23:42 ` Hannes Frederic Sowa
2013-12-10 2:04 ` David Miller
2013-12-08 14:47 ` [PATCH net-next 4/5] ipv6: add ip6_flowlabel helper Florent Fourcot
2013-12-09 23:42 ` Hannes Frederic Sowa
2013-12-10 2:04 ` David Miller
2013-12-08 14:47 ` [PATCH net-next 5/5] ipv6: use ip6_flowinfo helper Florent Fourcot
2013-12-09 23:42 ` Hannes Frederic Sowa
2013-12-10 2:04 ` David Miller
2013-12-09 23:41 ` [PATCH net-next 1/5] ipv6: add flowinfo for tcp6 pkt_options for all cases Hannes Frederic Sowa
2013-12-10 2:04 ` David Miller [this message]
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=20131209.210407.175864636691434095.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=florent.fourcot@enst-bretagne.fr \
--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).