Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+19\/26\]\s+net\/ipv6\:\s+switch\s+ipv6_flowlabel_opt\s+to\s+sockptr

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+19\/26\]\s+net\/ipv6\:\s+switch\s+ipv6_flowlabel_opt\s+to\s+sockptr_t\s*$/: 7 ]

Total 7 documents matching your query.

1. Re: [PATCH 19/26] net/ipv6: switch ipv6_flowlabel_opt to sockptr_t (score: 1): Author: Ido Schimmel <idosch@xxxxxxxxxx>; Date: Mon, 27 Jul 2020 21:22:59 +0300; Tested-by: Ido Schimmel <idosch@xxxxxxxxxxxx> Thanks!; /html/lvs-devel/2020-07/msg00146.html (14,882 bytes)
2. Re: [PATCH 19/26] net/ipv6: switch ipv6_flowlabel_opt to sockptr_t (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Mon, 27 Jul 2020 18:15:55 +0200; I have to admit I didn't spot the difference between the good and the bad output even after trying hard.. But can you try the patch below? -- sockptr_advance never properly worked. Replace it with _o; /html/lvs-devel/2020-07/msg00141.html (27,419 bytes)
3. Re: [PATCH 19/26] net/ipv6: switch ipv6_flowlabel_opt to sockptr_t (score: 1): Author: Ido Schimmel <idosch@xxxxxxxxxx>; Date: Mon, 27 Jul 2020 16:33:31 +0300; ``` ip link add name dummy10 up type dummy ping -q -F 0 -I dummy10 ff02::1 &> /dev/null & tcpdump -nne -e -i dummy10 -vvv -c 1 dst host ff02::1 pkill ping echo ping -F 0 -I dummy10 ff02::1 &> /dev/nu; /html/lvs-devel/2020-07/msg00136.html (17,185 bytes)
4. RE: [PATCH 19/26] net/ipv6: switch ipv6_flowlabel_opt to sockptr_t (score: 1): Author: David Laight <David.Laight@xxxxxxxxxx>; Date: Mon, 27 Jul 2020 13:24:45 +0000; Depending on the other checks you may also be able to cross from user addresses to kernel ones. At the minimum sockptr_advance() has to fail if the boundary would be crossed. The 'is this a kernel or; /html/lvs-devel/2020-07/msg00135.html (21,826 bytes)
5. Re: [PATCH 19/26] net/ipv6: switch ipv6_flowlabel_opt to sockptr_t (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Mon, 27 Jul 2020 15:00:29 +0200; Can you send a reproducer? We could do that, although I wouldn't add it to the existing functions to avoid the churns and instead add copy_to_sockptr_offset or something like that.; /html/lvs-devel/2020-07/msg00134.html (14,520 bytes)
6. Re: [PATCH 19/26] net/ipv6: switch ipv6_flowlabel_opt to sockptr_t (score: 1): Author: Ido Schimmel <idosch@xxxxxxxxxx>; Date: Mon, 27 Jul 2020 15:15:05 +0300; Christoph, I see a regression with IPv6 flowlabel that I bisected to this patch. When passing '-F 0' to 'ping' the flow label should be random, yet it's the same every time after this patch. It seems; /html/lvs-devel/2020-07/msg00133.html (19,401 bytes)
7. [PATCH 19/26] net/ipv6: switch ipv6_flowlabel_opt to sockptr_t (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Thu, 23 Jul 2020 08:09:01 +0200; Pass a sockptr_t to prepare for set_fs-less handling of the kernel pointer from bpf-cgroup. Note that the get case is pretty weird in that it actually copies data back to userspace from setsockopt. S; /html/lvs-devel/2020-07/msg00094.html (17,256 bytes)

Current List: 1 - 7
Page: [1]