public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: swarup <swarupkotikalapudi@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, shuah@kernel.org, hughd@google.com
Subject: Re: + selftests-proc-add-proc-pid-statm-output-validation.patch added to mm-nonmm-unstable branch
Date: Mon, 9 Oct 2023 23:48:49 +0530	[thread overview]
Message-ID: <ZSRECdGdkFjoMbz2@swarup-virtual-machine> (raw)
In-Reply-To: <f50cfce5-5e46-433f-be48-a8c733843457@p183>

esOn Mon, Oct 09, 2023 at 12:00:04PM +0300, Alexey Dobriyan wrote:
> On Mon, Oct 09, 2023 at 09:14:53AM +0300, Alexey Dobriyan wrote:
> > On Wed, Oct 04, 2023 at 01:17:00PM -0700, Andrew Morton wrote:
> 
> > > +		if (errno == ENOENT) {
> > > +			/*
> > > +			 * /proc/${pid}/statm is under CONFIG_PROC_PAGE_MONITOR,
> > > +			 * it doesn't necessarily exist.
> 
> Oh, and /proc/*/statm is _not_ under CONFIG_PROC_PAGE_MONITOR,
> it always exists.

Hi Alexey Dobriyan,
It is my mistake, i checked the code, yes it always exists.
Thanks,
Swarup

  reply	other threads:[~2023-10-09 18:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231004201701.87CB5C433C7@smtp.kernel.org>
2023-10-09  6:14 ` + selftests-proc-add-proc-pid-statm-output-validation.patch added to mm-nonmm-unstable branch Alexey Dobriyan
2023-10-09  9:00   ` Alexey Dobriyan
2023-10-09 18:18     ` swarup [this message]
2023-10-09 18:16   ` swarup
2023-10-09 19:20 ` [PATCH v3] selftests:proc Add /proc/$(pid)/statm output validation Swarup Laxman Kotiaklapudi
     [not found] <20231001193740.B716AC433C7@smtp.kernel.org>
2023-10-02 12:38 ` + selftests-proc-add-proc-pid-statm-output-validation.patch added to mm-nonmm-unstable branch Alexey Dobriyan
2023-10-02 17:52   ` swarup

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=ZSRECdGdkFjoMbz2@swarup-virtual-machine \
    --to=swarupkotikalapudi@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shuah@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