Andrew, This is a respin of the last fixes I sent for sock memcg problems with the static_keys enablement. The first patch is still unchanged, and for the second, I am using a flags field as for your suggestion. Indeed, I found a flags field to be more elegant, while still maintaining a fast path for the readers. Kame, will you please take a look and see if this would work okay? Tejun, are you happy with the current state of the comments explaining the scenario? Thank you very much for your time Glauber Costa (2): Always free struct memcg through schedule_work() decrement static keys on real destroy time include/linux/memcontrol.h | 5 ++++ include/net/sock.h | 11 +++++++++ mm/memcontrol.c | 53 +++++++++++++++++++++++++++++++++---------- net/ipv4/tcp_memcontrol.c | 34 ++++++++++++++++++++++----- 4 files changed, 83 insertions(+), 20 deletions(-) -- 1.7.7.6 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>