From bfef14acbcef934c202f0e6961538a01b2397c44 Mon Sep 17 00:00:00 2001 From: Itaru Kitayama Date: Wed, 5 Mar 2008 15:07:30 -0800 Subject: [PATCH] --- yaml --- r: 87054 b: refs/heads/master c: 989a7241df87526bfef0396567e71ebe53a84ae4 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/vm/slub.txt | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/[refs] b/[refs] index a9e52e9cc3e2..f1b5ebadffec 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 6d2144d355d2a532e5cc3fc12a6ba2a8d4ef15e4 +refs/heads/master: 989a7241df87526bfef0396567e71ebe53a84ae4 diff --git a/trunk/Documentation/vm/slub.txt b/trunk/Documentation/vm/slub.txt index dcf8bcf846d6..7c13f22a0c9e 100644 --- a/trunk/Documentation/vm/slub.txt +++ b/trunk/Documentation/vm/slub.txt @@ -50,14 +50,14 @@ F.e. in order to boot just with sanity checks and red zoning one would specify: Trying to find an issue in the dentry cache? Try - slub_debug=,dentry_cache + slub_debug=,dentry to only enable debugging on the dentry cache. Red zoning and tracking may realign the slab. We can just apply sanity checks to the dentry cache with - slub_debug=F,dentry_cache + slub_debug=F,dentry In case you forgot to enable debugging on the kernel command line: It is possible to enable debugging manually when the kernel is up. Look at the