From: Aaron Tomlin
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.
T
From: Aaron Tomlin
Add neg_one to the list of standard constraints.
Signed-off-by: Aaron Tomlin
Acked-by: Rik van Riel
---
kernel/sysctl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index 34a6047..dd531a6 100644
--- a/kernel/sysctl.c
+++ b/kernel/sy
From: Aaron Tomlin
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.
T
From: Aaron Tomlin
Add neg_one to the list of standard constraints.
Signed-off-by: Aaron Tomlin
---
kernel/sysctl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index 34a6047..dd531a6 100644
--- a/kernel/sysctl.c
+++ b/kernel/sysctl.c
@@ -122,6 +122,7 @
From: Aaron Tomlin
When khungtaskd detects hung tasks, it prints out
backtraces from a number of those tasks. Sometimes
the information on why things are stuck is hidden
in those backtraces. Limiting the number of
backtraces being printed out can result in the user
not seeing the information nece
From: Aaron Tomlin
When khungtaskd detects hung tasks, it prints out
backtraces from a number of those tasks. Sometimes
the information on why things are stuck is hidden
in those backtraces. Limiting the number of
backtraces being printed out can result in the user
not seeing the information nece
From: Aaron Tomlin
The khungtaskd thread limits how many hung task warnings it displays
at a time, when a timeout occurs. This patch allows that limit to be
set to "unlimited", by setting hung_task_warnings to -1, which will
cause khungtaskd to display information about all hung tasks.
While ULO
From: Aaron Tomlin
The khungtaskd thread limits how many hung task
warnings it displays at a time, when a timeout
occurs. This patch allows that limit to be set
to "unlimited", by setting hung_task_warnings
to -1, which will cause khungtaskd to display
information about all hung tasks.
While ULO
From: Aaron Tomlin
Add neg_one to the list of standard constraints.
Signed-off-by: Aaron Tomlin
---
kernel/sysctl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index 34a6047..dd531a6 100644
--- a/kernel/sysctl.c
+++ b/kernel/sysctl.c
@@ -122,6 +122,7 @
From: Aaron Tomlin
Enable hung_task_warnings to display every hung
task warning when set to -1.
Signed-off-by: Aaron Tomlin
---
include/linux/sched/sysctl.h | 2 +-
kernel/hung_task.c | 9 +
kernel/sysctl.c | 5 +++--
3 files changed, 9 insertions(+), 7 deletions
From: Aaron Tomlin
Add neg_one to the list of standard constraints.
Signed-off-by: Aaron Tomlin
---
kernel/sysctl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index 34a6047..dd531a6 100644
--- a/kernel/sysctl.c
+++ b/kernel/sysctl.c
@@ -122,6 +122,7 @
From: Aaron Tomlin
Enable hung_task_warnings to display every hung task warning, when
set to -1. While ULONG_MAX is practically "unlimited", this patch
takes it one step further. Note: The maximum is now 2^31-1 which
should (hopefully) be sufficient.
Please let me know your thoughts.
Aaron Toml
From: Aaron Tomlin
Since v1:
- Removed unnecessary parentheses (sergei.shtylyov)
---8<---
Failed GFP_ATOMIC allocations by the network stack result in dropped
packets, which will be received on a subsequent retransmit, and an
unnecessary, noisy warning with a kernel backtrace.
These warnings
From: Aaron Tomlin
Since v1:
- Removed unnecessary parentheses
---8<---
Failed GFP_ATOMIC allocations by the network stack result in dropped
packets, which will be received on a subsequent retransmit, and an
unnecessary, noisy warning with a kernel backtrace.
These warnings are harmless, but
From: Aaron Tomlin
Failed GFP_ATOMIC allocations by the network stack result in dropped
packets, which will be received on a subsequent retransmit, and an
unnecessary, noisy warning with a kernel backtrace.
These warnings are harmless, but they still cause users to panic and
file bug reports ove
From: Aaron Tomlin
Hi,
This patch is in response to BZ#42967 [1].
Using VM_BUG_ON so it's used only when CONFIG_DEBUG_VM is set,
given that cache_alloc_node() is a hot code path.
Cheers,
Aaron
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=42967
---8<---
mm: slab: Verify the nodeid pass
16 matches
Mail list logo