[02:45] <bgianf> Looks like you guys ported the following change to xenial's kernel tree: http://kernel.ubuntu.com/git/kernel-ppa/mirror/ubuntu-xenial.git/commit/mm?id=b56d2a75e1daae6ff6eedfb732eadf3c13df6090
[02:47] <bgianf> This introduced a bug (infinite loop) when using transparent huge pages.
[02:47] <bgianf> Fix is here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/mm/huge_memory.c?id=8310d48b125d19fcd9521d83b8293e63eb1646aa
[02:48] <bgianf> Everyone on my team is hitting this bug on xenial, what's the likely hood of getting the fix ported?
[03:29] <bgianf> Went ahead and file here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660518
[08:43] <smb> bgianf, Hm, looks like that FOLL_FORCE/FOLL_COW is already aked for (though for different reasons). There is hope to get it into this cycle
[08:47] <bgianf> smb, cool thanks for the info. Was there somewhere I could have looked to see that it was already asked for?
[08:47] <bgianf> Looked around briefly, didn't see anything...
[08:48] <smb> bgianf, It was on the kernel-team mailing list (think there is some archive, too, but probably hard to find by search)
[08:57] <smb> https://lists.ubuntu.com/archives/kernel-team/2017-January/082114.html
[09:02] <bgianf> thanks for the link! 
[13:45] <zioproto> hello all. I am new here. I would like some feedback about CONFIG_NET_DROP_MONITOR=n in the Ubuntu Kernel. It would be of great help to have it set to module. We use ubuntu for the openstack network node.
[13:50] <rtg> zioproto, I just set CONFIG_NET_DROP_MONITOR=m in what will become the Zesty kernel.
[13:50] <rtg> (based on your comment)
[13:50] <zioproto> thanks
[13:51] <zioproto> If this goes in Zesty I can package the application dropwatch for ubuntu
[13:51] <zioproto> at the moment is packaged only on Fedora
[13:52] <zioproto> https://fedorahosted.org/dropwatch/
[13:52] <zioproto> but it really needs that Kernel support
[13:54] <rtg> zioproto, It'll likely be a week or so before the 4.10 kernel gets promoted to the Zesty archive. (which is the version to which I've committed the CONFIG_NET_DROP_MONITOR patch)
[14:10] <zioproto> rtg, thanks ! how does it work for the Xenial kernels ?
[14:19] <rtg> zioproto, there doesn't seem to be a reason why it couldn't be set '=m'
[14:19] <rtg> zioproto, please file a bug and assign me to it
[14:29] <zioproto> rtg, here ? https://bugs.launchpad.net/~canonical-kernel-team
[14:31] <rtg> zioproto, https://bugs.launchpad.net/ubuntu/+filebug
[14:34] <zioproto> rtg, redirects to https://help.ubuntu.com/community/ReportingBugs
[14:34] <rtg> zioproto, maybe you have to be logged in
[14:34] <zioproto> rtg, this one works https://bugs.launchpad.net/ubuntu/+source/linux/+filebug
[14:35] <zioproto> maybe the +source/linux was missing ?
[14:37] <zioproto> rtg, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660634
[14:38] <zioproto> I cannot assign it to another person
[14:38] <zioproto> You may only assign yourself because you are not affiliated with this project and do not have any team memberships.
[14:40] <rtg> zioproto, done
[14:40] <zioproto> thanks!
[19:49] <zyga> ogasawara: hey, I'm sorry to bother you with such a tiny thing; I wrote a patch that exposes bind mount as a flag in mountinfo, do you think it makes sense to send this anywhere? http://paste.ubuntu.com/23901026/