It's convenient to have some reference point in the kernel version,
what git commit it refers to, so
+CONFIG_LOCALVERSION_AUTO=y
Note: kernel configs used during rpm packages creation do not have this option
enabled. So this is the first pecularity of configs committed to the kernel
tree for
In case kernel is built from the tree (not with help of rpmbuild),
KERNELRELEASE env variable is not provided and should be
constructed from local git tags.
Generated KERNELRELEASE example:
"3.10.0-229.7.2.ovz.9.10-1-g1da4621"
VZVERSION has been also aligned with format used in kernel.spec:
13.11.2015 16:40, Stanislav Kinsburskiу пишет:
Acked-by: Stanislav Kinsburskiy
BTW, have you checked, that this patch works as expected?
Just to make sure we didn't miss anything.
I have built the kernel RPMs with it and re-checked that this "mount bomb"
13 нояб. 2015 г. 14:58 пользователь Evgenii Shatokhin
написал:
>
> 13.11.2015 16:40, Stanislav Kinsburskiу пишет:
> > Acked-by: Stanislav Kinsburskiy
> >
> > BTW, have you checked, that this patch works as expected?
> > Just to make sure we didn't
13 нояб. 2015 г. 14:58 пользователь Evgenii Shatokhin
написал:
>
> 13.11.2015 16:40, Stanislav Kinsburskiу пишет:
> > Acked-by: Stanislav Kinsburskiy
> >
> > BTW, have you checked, that this patch works as expected?
> > Just to make sure we didn't
Stas, please put reviewer to CC.
Volodya, please review.
--
Best regards,
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
On 11/12/2015 09:01 PM, Stanislav Kinsburskiy wrote:
This patch defines arch_free_page() callback to x86 architecture. The only
thing it does is pages contents zeroing.
Acked-by: Stanislav Kinsburskiy
BTW, have you checked, that this patch works as expected?
Just to make sure we didn't miss anything.
13 нояб. 2015 г. 14:01 пользователь Evgenii Shatokhin
написал:
>
> https://jira.sw.ru/browse/PSBM-34438
>
> (This
https://jira.sw.ru/browse/PSBM-34438
(This fix was adapted from PCS6.)
It is possible for a container to create lots of mount points, which may
make operations with them slower. As some of these operations take
global locks (namespace_sem, vfsmount_lock), it might affect other
containers as