From: Michal Hocko <mhocko@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Shakeel Butt <shakeel.butt@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
kernel-team@meta.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Kyle McMartin <kyle@infradead.org>
Subject: Re: [PATCH] mm: ratelimit oversized kvmalloc warnings instead of once
Date: Wed, 19 Jun 2024 21:54:48 +0200 [thread overview]
Message-ID: <ZnM3iFLPtFVVmCpR@tiehlicka> (raw)
In-Reply-To: <CAHk-=whXL32xG1HWGaVaOkHf+g407upYbvZeZgmhnsxn2R+JRQ@mail.gmail.com>
On Wed 19-06-24 12:30:42, Linus Torvalds wrote:
> On Wed, 19 Jun 2024 at 10:47, Shakeel Butt <shakeel.butt@linux.dev> wrote:
> >
> > Linus, please let me know if you have any concerns on the approach
> > Michal is suggesting i.e. a variant for warn once for unique call stack.
>
> I think we should just try to change the existing WARN_ONCE(), and see
> if it causes any issues.
>
> A new "WARN_UNIQUE()" might be the borign and safe approach, but
>
> (a) it won't actually be unique if you don't have stackdepot anyway,
> and will just be WARN_ONCE
>
> (b) I suspect most WARN_ONCE users really do want WARN_UNIQUE
>
> so let's at least _start_ with just changing semantics of the existing
> "once", and then if it causes problems we'll have to revisit this.
>
> I doubt it will cause problems,
I would be careful about the WARN_ONCE used from stackdepot itself. It's
been some time since I have looked into that code but a quick grep tells
there is some usage.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2024-06-19 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 21:34 Shakeel Butt
2024-06-18 21:40 ` Linus Torvalds
2024-06-18 21:44 ` Shakeel Butt
2024-06-19 7:19 ` Michal Hocko
2024-06-19 8:03 ` Shakeel Butt
2024-06-19 8:30 ` Michal Hocko
2024-06-19 8:37 ` Shakeel Butt
2024-06-19 8:48 ` Michal Hocko
2024-06-19 17:47 ` Shakeel Butt
2024-06-19 19:30 ` Linus Torvalds
2024-06-19 19:54 ` Michal Hocko [this message]
2024-06-19 12:49 ` Mateusz Guzik
2024-06-19 12:51 ` Mateusz Guzik
2024-06-19 17:52 ` Shakeel Butt
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=ZnM3iFLPtFVVmCpR@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@meta.com \
--cc=kyle@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shakeel.butt@linux.dev \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox