From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Thomas Gleixner <tglx@linutronix.de>,
Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
Iurii Zaikin <yzaikin@google.com>,
Mel Gorman <mgorman@techsingularity.net>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH 2/2 v3] mm/compaction: Disable compact_unevictable_allowed on RT
Date: Wed, 4 Mar 2020 10:27:48 +0100 [thread overview]
Message-ID: <20200304092748.dz5m57hmwirpk65y@linutronix.de> (raw)
In-Reply-To: <bb5bdf8a-67f0-565b-33a1-8cff6f205f2e@suse.cz>
On 2020-03-04 09:19:21 [+0100], Vlastimil Babka wrote:
> >> + WARN_ONCE(old != *(int *)table->data, "sysctl attribute %s changed.",
> >> + table->procname);
> >
> > The WARN will include a stack trace which just isn't interesting. A
> > pr_warn() would be better?
>
> Yeah, the only interesting part of full WARN would possibly be, which process
> changed it. That might be useful to print.
Yes, the stack trace and register dump isn't interesting. But as
Vlastimil says, the task and pid are informative. So if that is too much
I could extract those two informations and include it in a pr_warn().
Sebastian
next prev parent reply other threads:[~2020-03-04 9:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 16:10 [PATCH] mm/compaction: Disable compact_unevictable_allowed on RT Sebastian Andrzej Siewior
[not found] ` <20200115161035.893221-1-bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2020-01-15 22:04 ` Vlastimil Babka
2020-01-15 22:04 ` Vlastimil Babka
2020-01-16 10:22 ` Sebastian Andrzej Siewior
2020-03-02 17:35 ` [PATCH v2] " Sebastian Andrzej Siewior
2020-03-02 21:25 ` Andrew Morton
2020-03-03 17:59 ` Sebastian Andrzej Siewior
2020-03-03 20:20 ` [PATCH 1/2] =?UTF-8?q?mm/compaction:=20Really=20limit=20compact?= =?UTF-8?q?=5Funevictable=5Fallowed=20to=200=E2=80=A61?= Sebastian Andrzej Siewior
2020-03-03 20:22 ` [PATCH 2/2 v3] mm/compaction: Disable compact_unevictable_allowed on RT Sebastian Andrzej Siewior
2020-03-03 23:56 ` Andrew Morton
2020-03-04 8:19 ` Vlastimil Babka
2020-03-04 9:27 ` Sebastian Andrzej Siewior [this message]
2020-03-19 16:39 ` [PATCH 2/2 v4] " Sebastian Andrzej Siewior
2020-03-19 16:49 ` Vlastimil Babka
2020-03-19 16:55 ` [PATCH 2/2 v5] " Sebastian Andrzej Siewior
2020-03-04 8:18 ` [PATCH 2/2 v3] " Vlastimil Babka
2020-03-04 9:25 ` Sebastian Andrzej Siewior
2020-03-04 9:11 ` Mel Gorman
2020-03-04 8:12 ` [PATCH 1/2] mm/compaction: Really limit compact_unevictable_allowed to 0…1 Vlastimil Babka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200304092748.dz5m57hmwirpk65y@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=mgorman@techsingularity.net \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=yzaikin@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.