public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Greg KH <greg@kroah.com>
Cc: Dan Jacobson <jidanni@jidanni.org>, stable@vger.kernel.org
Subject: Re: Say that it was Linux that printed "Out of memory"
Date: Sun, 26 Nov 2023 10:20:44 +0100	[thread overview]
Message-ID: <20231126092044.GA7407@1wt.eu> (raw)
In-Reply-To: <2023112613-decorator-unroasted-500d@gregkh>

On Sun, Nov 26, 2023 at 08:48:50AM +0000, Greg KH wrote:
> On Sun, Nov 26, 2023 at 10:40:36AM +0800, Dan Jacobson wrote:
> > In https://github.com/szabgab/perlmaven.com/issues/583 we see to find the
> > simple answer to "What printed 'Out of memory', one must consult the
> > experts.
> > 
> > Therefore the "Out of memory" message needs to be prefixed with the name of
> > the kernel, or something. Anything. Thanks.
> 
> Prefixed exactly where?  The kernel already does report all of this to
> the kernel log, saying what program was killed due to out of memory
> issues.

From what I can see on the original article featuring a simple perl
script at https://perlmaven.com/out-of-memory it says "on the terminal".
As such, it's just the perl interpreter that faced ENOMEM and printed
the corresponding message before quitting. One will note that there is
absolutely no capture provided in the article nor the reporter to ease
understanding, but as a rule of thumb the kernel will not print stuff
in the user's terminal, it will only appear in logs where it's indeed
prefixed. And no need for an "expert" to figure that ;-)

Willy

  reply	other threads:[~2023-11-26  9:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26  2:40 Say that it was Linux that printed "Out of memory" Dan Jacobson
2023-11-26  8:48 ` Greg KH
2023-11-26  9:20   ` Willy Tarreau [this message]
2023-11-26 13:25     ` Dan Jacobson
2023-11-26 13:15   ` Dan Jacobson

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=20231126092044.GA7407@1wt.eu \
    --to=w@1wt.eu \
    --cc=greg@kroah.com \
    --cc=jidanni@jidanni.org \
    --cc=stable@vger.kernel.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