From: pintu@codeaurora.org
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org, pintu.ping@gmail.com
Subject: Re: [PATCH] mm/util.c: Add error logs for commitment overflow
Date: Fri, 02 Oct 2020 21:48:11 +0530 [thread overview]
Message-ID: <783f85abc401aa9dbe7623819f9683fb@codeaurora.org> (raw)
In-Reply-To: <20201002121137.GY20115@casper.infradead.org>
On 2020-10-02 17:41, Matthew Wilcox wrote:
>
> I don't think the __func__ is particularly useful information. I would
> also expect the name of the process to be more interesting than the
> PID.
> And why is the ppid useful?
>
Dear Matthew, First, thank you so much for your review and comments.
I totally agree with you.
Yes, initially I included process-name but later removed it to shrink
some lines.
I thought just pid should be enough to figure out the culprit process
from dumps.
Okay, I agree __func__ can also be removed.
ppid, I thought might be useful, so I included it. Okay I will remove
that too.
> Wouldn't this message be more useful?
>
> fork: Would overcommit system (pid:162 name:./consume-and-fork.out)
>
Okay, yes I think this should be sufficient.
But I think printing pages also should be good to indicate the users to
lack
information about this commitment.
> ie put it in dup_mmap() and use current->comm
Sorry, this part about dup_mmap(), I could not understand.
Thanks,
Pintu
next prev parent reply other threads:[~2020-10-02 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 11:57 [PATCH] mm/util.c: Add error logs for commitment overflow Pintu Kumar
2020-10-02 12:11 ` Matthew Wilcox
2020-10-02 16:18 ` pintu [this message]
2020-10-02 12:17 ` Michal Hocko
2020-10-02 16:23 ` pintu
2020-10-05 7:20 ` Michal Hocko
2020-10-19 3:02 ` pintu
2020-10-19 13:06 ` Michal Hocko
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=783f85abc401aa9dbe7623819f9683fb@codeaurora.org \
--to=pintu@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pintu.ping@gmail.com \
--cc=willy@infradead.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 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.