[Devel] [PATCH rh7 3/4] ms/locking/lockdep: Provide lockdep_assert{, _once}() helpers

From: Peter Zijlstra Extract lockdep_assert{,_once}() helpers to more easily write composite assertions like, for example: lockdep_assert(lockdep_is_held(&drm_device.master_mutex) || lockdep_is_held(&drm_file.master_lookup_lock)); Signed-off-by: Peter Zijlstra (In

[Devel] [PATCH rh7 1/4] ms/lockdep: Add lockdep_assert_not_held()

From: Shuah Khan Some kernel functions must be called without holding a specific lock. Add lockdep_assert_not_held() to be used in these functions to detect incorrect calls while holding a lock. lockdep_assert_not_held() provides the opposite functionality of lockdep_assert_held() which is used

[Devel] [PATCH rh7 4/4] oom: Cast the lockdep spell in the code

task_will_free_mem() requires the task_lock lock is held or the function is called on the current, but this is just a function comment, let's add the proper lockdep check according to this comment. https://jira.sw.ru/browse/PSBM-143283 Signed-off-by: Konstantin Khorenko Suggested-by: Nikolay Bor

[Devel] [PATCH rh7 2/4] ms/lockdep: Add lockdep lock state defines

From: Shuah Khan Adds defines for lock state returns from lock_is_held_type() based on Johannes Berg's suggestions as it make it easier to read and maintain the lock states. These are defines and a enum to avoid changes to lock_is_held_type() and lockdep_is_held() return types. Updates to lock_i

Re: [Devel] [PATCH rh7 1/2] oom: Do not mark victim a task without mm

-- Best regards, Konstantin Khorenko, Virtuozzo Linux Kernel Team On 26.11.2022 23:15, nb wrote: On 23.11.22 г. 20:53 ч., Konstantin Khorenko wrote: Currently it's possible to mark a task as a victim even in case it has already cleared its ->mm. This might lead (and leads) to a situation

[Devel] [PATCH RHEL7 COMMIT] oom: Do not mark victim a task without mm

The commit is pushed to "branch-rh7-3.10.0-1160.80.1.vz7.190.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-1160.80.1.vz7.190.1 --> commit 4009eb1c432a03133677eb76008f9063b9f9b443 Author: Konstantin Khorenko Date: Wed Nov 23 20:58:56 2022 +0300 o

[Devel] [PATCH RHEL7 COMMIT] oom: Drop the OOM timeout message

The commit is pushed to "branch-rh7-3.10.0-1160.80.1.vz7.190.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-1160.80.1.vz7.190.1 --> commit f3efd4f04c384f2d2e16db4f5a6b8b41174906ae Author: Konstantin Khorenko Date: Wed Nov 23 19:00:40 2022 +0300 o

[Devel] [PATCH RHEL7 COMMIT] ms/lockdep: Add lockdep_assert_not_held()

The commit is pushed to "branch-rh7-3.10.0-1160.80.1.vz7.190.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-1160.80.1.vz7.190.1 --> commit 542557c8c8bc38655ef771acca6a7d213a728ccc Author: Shuah Khan Date: Fri Feb 26 17:06:58 2021 -0700 ms/lockdep

[Devel] [PATCH RHEL7 COMMIT] ms/lockdep: Add lockdep lock state defines

The commit is pushed to "branch-rh7-3.10.0-1160.80.1.vz7.190.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-1160.80.1.vz7.190.1 --> commit 3277a00d3ddc427c8d12be92287b51e1c42b1203 Author: Shuah Khan Date: Fri Feb 26 17:06:59 2021 -0700 ms/lockdep

[Devel] [PATCH RHEL7 COMMIT] ms/locking/lockdep: Provide lockdep_assert{, _once}() helpers

The commit is pushed to "branch-rh7-3.10.0-1160.80.1.vz7.190.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-1160.80.1.vz7.190.1 --> commit c7e3b0fe08e47762cc7ab4c46547e53844f4b8b5 Author: Peter Zijlstra Date: Mon Aug 2 18:59:56 2021 +0800 ms/lock

[Devel] [PATCH RHEL7 COMMIT] oom: Cast the lockdep spell in the code

The commit is pushed to "branch-rh7-3.10.0-1160.80.1.vz7.190.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh7-3.10.0-1160.80.1.vz7.190.1 --> commit acce6e8d56cbd2730d12ca3bcd6399d3df3135eb Author: Konstantin Khorenko Date: Mon Nov 28 17:44:17 2022 +0300 o

[Devel] [PATCH RHEL9 COMMIT] ms/locking/lockdep: Provide lockdep_assert{, _once}() helpers

The commit is pushed to "branch-rh9-5.14.0-70.22.1.vz9.17.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh9-5.14.0-70.22.1.vz9.17.11 --> commit d9dda981a07a092458c78a988923e746aec3a970 Author: Peter Zijlstra Date: Mon Aug 2 18:59:56 2021 +0800 ms/locking/l

[Devel] [PATCH RHEL9 COMMIT] oom: Cast the lockdep spell in the code

The commit is pushed to "branch-rh9-5.14.0-70.22.1.vz9.17.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git after rh9-5.14.0-70.22.1.vz9.17.11 --> commit 0b9d9d056113db1de9529d3185c2f0b2fba46e1e Author: Konstantin Khorenko Date: Mon Nov 28 20:13:14 2022 +0300 oom: C

[Devel] [PATCH vz7] devtmpfs: fix the dangling pointer of global devtmpfsd thread

When the devtmpfs fails to mount, a dangling pointer still remains in global. Specifically, the err variable is passed by a pointer to the devtmpfsd. When the devtmpfsd exits, it sets the error and completes the setup_done. In this situation, the thread pointer is not set to null. After the devtmpf

[Devel] [PATCH vz7] fs/namespace.c: WARN if mnt_count has become negative

Missing calls to mntget() (or equivalently, too many calls to mntput()) are hard to detect because mntput() delays freeing mounts using task_work_add(), then again using call_rcu(). As a result, mnt_count can often be decremented to -1 without getting a KASAN use-after-free report. Such cases are

[Devel] [PATCH vz7] proc: Handle umounts cleanly

syzbot writes: > KASAN: use-after-free Read in dput (2) > > proc_fill_super: allocate dentry failed > == > BUG: KASAN: use-after-free in fast_dput fs/dcache.c:727 [inline] > BUG: KASAN: use-after-free in dput+0x53e/0xdf0 fs/dcache.c:84