| lists.openwall.net | 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1390474563-15424-1-git-send-email-atomlin@redhat.com> Date: Thu, 23 Jan 2014 10:56:01 +0000 From: Aaron Tomlin <atomlin@...hat.com> To: mingo@...nel.org Cc: linux-kernel@...r.kernel.org, rientjes@...gle.com, mingo@...hat.com, oleg@...hat.com, riel@...hat.com, akpm@...ux-foundation.org, atomlin@...hat.com Subject: [RFC PATCH v5 0/2] hung_task: Display every hung task warning When khungtaskd detects hung tasks, it prints out backtraces from a number of those tasks. Limiting the number of backtraces being printed out can result in the user not seeing the information necessary to debug the issue. The hung_task_warnings sysctl controls this feature. This patch makes it possible for hung_task_warnings to accept a special value to print an unlimited number of backtraces when khungtaskd detects hung tasks. The special value is -1. To use this value it is necessary to change types from ulong to int. Rebased against v3.13-rc8. Changes since v4: - Improve the documentation on hung_task_warnings Changes since v3: - Simplify the commit message (Rik van Riel and David Rientjes) - Document hung_task_* sysctl parameters (David Rientjes) Aaron Tomlin (2): sysctl: Make neg_one a standard constraint hung_task: Display every hung task warning Documentation/sysctl/kernel.txt | 42 +++++++++++++++++++++++++++++++++++++++++ include/linux/sched/sysctl.h | 2 +- kernel/hung_task.c | 6 ++++-- kernel/sysctl.c | 6 ++++-- 4 files changed, 51 insertions(+), 5 deletions(-) -- 1.8.4.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists