lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 18 Nov 2019 17:24:33 -0800
From:   Brendan Higgins <>
To:     Luis Chamberlain <>
Cc:     Alan Maguire <>,
        Shuah Khan <>,
        "open list:KERNEL SELFTEST FRAMEWORK" 
        Linux Kernel Mailing List <>,
        KUnit Development <>,
        Kees Cook <>,
        Iurii Zaikin <>,
        Andrew Morton <>,
        Masahiro Yamada <>,,,,,,,
        Jonathan Corbet <>,
        "Theodore Ts'o" <>,,,,
        "open list:DOCUMENTATION" <>,
        Stephen Boyd <>,
        Knut Omang <>
Subject: Re: [PATCH v4 linux-kselftest-test 4/6] kunit: remove timeout
 dependence on sysctl_hung_task_timeout_seconds

On Mon, Nov 18, 2019 at 2:10 PM Luis Chamberlain <> wrote:
> On Fri, Nov 15, 2019 at 10:16:10AM +0000, Alan Maguire wrote:
> > In discussion of how to handle timeouts, it was noted that if
> > sysctl_hung_task_timeout_seconds is exceeded for a kunit test,
> > the test task will be killed and an oops generated.  This should
> > suffice as a means of debugging such timeout issues for now.
> >
> > Hence remove use of sysctl_hung_task_timeout_secs, which has the
> > added benefit of avoiding the need to export that symbol from
> > the core kernel.
> >
> > Signed-off-by: Alan Maguire <>
> > Signed-off-by: Knut Omang <>
> This seems like a workaround for sysctl_hung_task_timeout_secs not being
> exported. If true, this can be addressed by creating a symbol namespace
> (new) and using that namespace on this path.

It is; as discussed on in v3[1]. I don't really feel strongly one way
or the other, I can see arguments for either side. Still, I don't want
to give Alan the run-around. I think this is the 3rd or 4th time he
has tried to address this issue.


Powered by blists - more mailing lists