All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Robert Ho <robert.hu@intel.com>,
	pbonzini@redhat.com, akpm@linux-foundation.org,
	dan.j.williams@intel.com, dave.hansen@intel.com,
	guangrong.xiao@linux.intel.com, gleb@kernel.org,
	mtosatti@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, stefanha@redhat.com,
	yuhuang@redhat.com, linux-mm@kvack.org,
	ross.zwisler@linux.intel.com
Subject: Re: [PATCH v3 1/2] mm, proc: Fix region lost in /proc/self/smaps
Date: Fri, 23 Sep 2016 17:53:51 +0200	[thread overview]
Message-ID: <20160923155351.GA1584@redhat.com> (raw)
In-Reply-To: <20160923145301.GU4478@dhcp22.suse.cz>

On 09/23, Michal Hocko wrote:
>
> On Fri 23-09-16 15:56:36, Oleg Nesterov wrote:
> > 
> > I think we can simplify this patch. And imo make it better. How about
> 
> it is certainly less subtle because it doesn't report "sub-vmas".
> 
> > 	if (last_addr) {
> > 		vma = find_vma(mm, last_addr - 1);
> > 		if (vma && vma->vm_start <= last_addr)
> > 			vma = m_next_vma(priv, vma);
> > 		if (vma)
> > 			return vma;
> > 	}
> 
> we would still miss a VMA if the last one got shrunk/split

Not sure I understand what you mean... If the last one was split
we probably should not report the new vma. Nevermind, in any case
yes, sure, this can't "fix" other corner cases.

> So definitely an improvement but
> I guess we really want to document that only full reads provide a
> consistent (at some moment in time) output.

or all the threads were stopped. Agreed. And again, this applies to
any file in /proc.

Oleg.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Oleg Nesterov <oleg@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Robert Ho <robert.hu@intel.com>,
	pbonzini@redhat.com, akpm@linux-foundation.org,
	dan.j.williams@intel.com, dave.hansen@intel.com,
	guangrong.xiao@linux.intel.com, gleb@kernel.org,
	mtosatti@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, stefanha@redhat.com,
	yuhuang@redhat.com, linux-mm@kvack.org,
	ross.zwisler@linux.intel.com
Subject: Re: [PATCH v3 1/2] mm, proc: Fix region lost in /proc/self/smaps
Date: Fri, 23 Sep 2016 17:53:51 +0200	[thread overview]
Message-ID: <20160923155351.GA1584@redhat.com> (raw)
In-Reply-To: <20160923145301.GU4478@dhcp22.suse.cz>

On 09/23, Michal Hocko wrote:
>
> On Fri 23-09-16 15:56:36, Oleg Nesterov wrote:
> > 
> > I think we can simplify this patch. And imo make it better. How about
> 
> it is certainly less subtle because it doesn't report "sub-vmas".
> 
> > 	if (last_addr) {
> > 		vma = find_vma(mm, last_addr - 1);
> > 		if (vma && vma->vm_start <= last_addr)
> > 			vma = m_next_vma(priv, vma);
> > 		if (vma)
> > 			return vma;
> > 	}
> 
> we would still miss a VMA if the last one got shrunk/split

Not sure I understand what you mean... If the last one was split
we probably should not report the new vma. Nevermind, in any case
yes, sure, this can't "fix" other corner cases.

> So definitely an improvement but
> I guess we really want to document that only full reads provide a
> consistent (at some moment in time) output.

or all the threads were stopped. Agreed. And again, this applies to
any file in /proc.

Oleg.

  reply	other threads:[~2016-09-23 15:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23 13:12 [PATCH v3 1/2] mm, proc: Fix region lost in /proc/self/smaps Robert Ho
2016-09-23 13:12 ` Robert Ho
2016-09-23 13:12 ` [PATCH v3 2/2] Documentation/filesystems/proc.txt: Add more description for maps/smaps Robert Ho
2016-09-23 13:12   ` Robert Ho
2016-09-23 16:06   ` Dave Hansen
2016-09-23 16:06     ` Dave Hansen
2016-09-28  2:27     ` Robert Hu
2016-09-23 13:50 ` [PATCH v3 1/2] mm, proc: Fix region lost in /proc/self/smaps Michal Hocko
2016-09-23 13:50   ` Michal Hocko
2016-09-23 14:39   ` Michal Hocko
2016-09-23 14:39     ` Michal Hocko
2016-09-23 13:56 ` Oleg Nesterov
2016-09-23 13:56   ` Oleg Nesterov
2016-09-23 14:53   ` Michal Hocko
2016-09-23 14:53     ` Michal Hocko
2016-09-23 15:53     ` Oleg Nesterov [this message]
2016-09-23 15:53       ` Oleg Nesterov
2016-09-26  8:46       ` Michal Hocko
2016-09-26  8:46         ` Michal Hocko
2016-09-29 13:14         ` Robert Hu
2016-09-29 13:42           ` Michal Hocko
2016-09-29 13:42             ` Michal Hocko
2016-09-29 13:05     ` Robert Hu

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=20160923155351.GA1584@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=gleb@kernel.org \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=robert.hu@intel.com \
    --cc=ross.zwisler@linux.intel.com \
    --cc=stefanha@redhat.com \
    --cc=yuhuang@redhat.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.