Now that CONFIG_DEPT_AGGRESSIVE_TIMEOUT_WAIT was introduced, apply the
consideration to swait, assuming an input 'ret' in ___swait_event()
macro is used as a timeout value.

Signed-off-by: Byungchul Park <max.byungchul.p...@gmail.com>
---
 include/linux/swait.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/swait.h b/include/linux/swait.h
index 0284821..def1e47 100644
--- a/include/linux/swait.h
+++ b/include/linux/swait.h
@@ -162,7 +162,7 @@ static inline bool swq_has_sleeper(struct swait_queue_head 
*wq)
        struct swait_queue __wait;                                      \
        long __ret = ret;                                               \
                                                                        \
-       sdt_might_sleep_start(NULL);                                    \
+       sdt_might_sleep_start_timeout(NULL, __ret);                     \
        INIT_LIST_HEAD(&__wait.task_list);                              \
        for (;;) {                                                      \
                long __int = prepare_to_swait_event(&wq, &__wait, state);\
-- 
1.9.1

Reply via email to