[lkml]   [2020]   [Jun]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH 0/5] kmod/umh: a few fixes
From: Luis Chamberlain <>

Tiezhu Yang had sent out a patch set with a slew of kmod selftest
fixes, and one patch which modified kmod to return 254 when a module
was not found. This opened up pandora's box about why that was being
used for and low and behold its because when UMH_WAIT_PROC is used
we call a kernel_wait4() call but have never unwrapped the error code.
The commit log for that fix details the rationale for the approach
taken. I'd appreciate some review on that, in particular nfs folks
as it seems a case was never really hit before.

This goes boot tested, selftested with kmod, and 0-day gives its
build blessings.

Luis Chamberlain (2):
umh: fix processed error when UMH_WAIT_PROC is used
selftests: simplify kmod failure value

Tiezhu Yang (3):
selftests: kmod: Use variable NAME in kmod_test_0001()
kmod: Remove redundant "be an" in the comment
test_kmod: Avoid potential double free in trigger_config_run_type()

drivers/block/drbd/drbd_nl.c | 20 +++++------
fs/nfsd/nfs4recover.c | 2 +-
include/linux/sched/task.h | 13 ++++++++
kernel/kmod.c | 5 ++-
kernel/umh.c | 4 +--
lib/test_kmod.c | 2 +-
net/bridge/br_stp_if.c | 10 ++----
security/keys/request_key.c | 2 +-
tools/testing/selftests/kmod/ | 50 +++++++++++++++++++++++-----
9 files changed, 71 insertions(+), 37 deletions(-)


 \ /
  Last update: 2020-06-10 17:50    [W:0.152 / U:39.280 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site