No, we don't.
But this one could be applied: "tests: do not try to read more than packet in
AutoFS test"
09.09.2017 02:01, Andrei Vagin пишет:
> On Thu, Aug 31, 2017 at 12:10:40PM +0300, Stanislav Kinsburskiy wrote:
>> Plus some cleanup.
>
> Do we need this patch for the upstream criu? Could you
This renames 'ret' variable to 'shrunk' as it used to count
shrunk extents.
This patch is the lost hunk from the upstream version of
patch "fs: convert fs shrinkers to new scan/count API",
which doesn't present in our backport:
9d22f7aba1b7ee7014fadd042a49be27a308ff74
Author: Vladimir Davydov
Dat
From: Zheng Liu
commit edaa53cac8fd4b96ed4b8f96c4933158ff2dd337 upstream.
In this commit we discard the lru algorithm for inodes with extent
status tree because it takes significant effort to maintain a lru list
in extent status tree shrinker and the shrinker can take a long time to
scan this lr
From: Zheng Liu
commit e963bb1de415ab06693357336c1bec664753e1e2 upsteam.
This commit improves the trace point of extents status tree. We rename
trace_ext4_es_shrink_enter in ext4_es_count() because it is also used
in ext4_es_scan() and we can not identify them from the result.
Further this com
From: Zheng Liu
commit eb68d0e2fc5a4e5c06324ea5f485fccbae626d05 upstream.
This commit adds some statictics in extent status tree shrinker. The
purpose to add these is that we want to collect more details when we
encounter a stall caused by extent status tree shrinker. Here we count
the followi
On Sun, Jul 23, 2017 at 6:15 PM, Cyrill Gorcunov wrote:
> We are carrying uids/gids in per-thread way since v1.8,
> so no need to require them to match anymore. We still
> require seccomp to match though. Need to revisit, seems
> may relax this requirement as well.
>
> https://jira.sw.ru/browse/PS
On Tue, Sep 12, 2017 at 5:43 PM, Cyrill Gorcunov wrote:
> On Sun, Jul 23, 2017 at 6:15 PM, Cyrill Gorcunov wrote:
>> We are carrying uids/gids in per-thread way since v1.8,
>> so no need to require them to match anymore. We still
>> require seccomp to match though. Need to revisit, seems
>> may r
Looks like we don't have devices, using it. Or lost some patches.
Anyway, currently it doesn't work. To make this VE namespace work, "namespace"
callback has to be added to ve_kobj_type. And this callback has to get VE
structure from kobject somehow. IOW, device has to be allocated per-ve.
Another
