[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191118220958.GS11244@42.do-not-panic.com>
Date: Mon, 18 Nov 2019 22:09:58 +0000
From: Luis Chamberlain <mcgrof@...nel.org>
To: Alan Maguire <alan.maguire@...cle.com>
Cc: brendanhiggins@...gle.com, skhan@...uxfoundation.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
kunit-dev@...glegroups.com, keescook@...omium.org,
yzaikin@...gle.com, akpm@...ux-foundation.org,
yamada.masahiro@...ionext.com, catalin.marinas@....com,
joe.lawrence@...hat.com, penguin-kernel@...ove.sakura.ne.jp,
schowdary@...dia.com, urezki@...il.com,
andriy.shevchenko@...ux.intel.com, corbet@....net, tytso@....edu,
adilger.kernel@...ger.ca, changbin.du@...el.com,
linux-ext4@...r.kernel.org, linux-doc@...r.kernel.org,
sboyd@...nel.org, Knut Omang <knut.omang@...cle.com>
Subject: Re: [PATCH v4 linux-kselftest-test 4/6] kunit: remove timeout
dependence on sysctl_hung_task_timeout_seconds
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 <alan.maguire@...cle.com>
> Signed-off-by: Knut Omang <knut.omang@...cle.com>
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.
Luis
Powered by blists - more mailing lists