From: Hagen Paul Pfeifer <hagen@xxxxxxxx> Date: Mon, 19 Jan 2015 15:00:21 +0100 > On 19 January 2015 at 14:55, Hannes Frederic Sowa > <hannes@xxxxxxxxxxxxxxxxxxx> wrote: >> Acked-by: Hannes Frederic Sowa <hannes@xxxxxxxxxxxxxxxxxxx> >> >> I think this is the correct way forward on how to deal with atomic >> fragments. >> >> Hagen, do you submit patches to remove dst_allfrag/RTAX_FEATURE_ALLFRAG, >> IPCORK_ALLFRAG, etc. for net-next, too? > > Yes, patch sits already in the pipe. I wanted to wait for davem's pull. It's one thing to change policy about how we might or might not automatically set this bit in the kernel, but at a minimum you cannot just remove RTAX_FEATURE_ALLFRAG, it's in a userspace header and you'll break application builds. Second of all, there is absolutely no reason to prevent the user from setting this bit. If someone wants to set RTAX_FEATURE_ALLFRAG on a route on their own system, that is their business. -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html