users should upgrade.
The LWN.net Weekly Edition for December 13, 2018 is available.
I propose that we make CONFIG_X86_X32 depend on BROKEN for a release
or two and then remove all the code if no one complains. If anyone
wants to re-add it, IMO they’re welcome to do so, but they need to do
it in a way that is maintainable.
If there are x32 users out there, now would be a good time for them to
In the RDMA microconference of the 2018 Linux Plumbers Conference (LPC),
John Hubbard, Dan Williams, and Matthew Wilcox led a discussion on the
problems surrounding get_user_pages() (and friends) and the
interaction with DMA. It is not the first time the topic has come up,
there was also a discussion about it at the
Linux Storage, Filesystem, and Memory-Management Summit back in April. In
a nutshell, the problem is that multiple parts of the kernel think they
have responsibility for the same chunk of memory, but they do not
coordinate their activities; as might be guessed, mayhem can sometimes ensue.
Git does not handle large files very well. While there is
work underway to handle large repositories through the commit
graph work, Git’s internal design has remained surprisingly constant
throughout its history, which means that storing large files into Git comes
with a significant and, ultimately, prohibitive performance
cost. Thankfully, other projects are helping Git address this
challenge. This article compares how Git LFS and git-annex address this problem
and should help readers pick the right solution for their needs.
There are a lot of claims regarding the relative security of containers
versus virtual machines (VMs), but there has been little in the way of
actually trying to measure those differences. James Bottomley gave a talk
refereed track of the 2018 Linux Plumbers Conference (LPC)
that described work that targets filling in that gap. He and his colleagues
have come up with
a measure that, while not perfect, gives a starting point for further