linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: robert.hu@intel.com
Cc: pbonzini@redhat.com, akpm@linux-foundation.org, oleg@redhat.com,
	dave.hansen@intel.com, dan.j.williams@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 v4 1/2] mm, proc: Fix region lost in /proc/self/smaps
Date: Fri, 7 Oct 2016 10:29:53 +0200	[thread overview]
Message-ID: <20161007082952.GI18439@dhcp22.suse.cz> (raw)
In-Reply-To: <1475806642.6073.10.camel@vmm.sh.intel.com>

On Fri 07-10-16 10:17:22, Robert Hu wrote:
> On Mon, 2016-10-03 at 13:52 +0200, Michal Hocko wrote:
> > On Sat 01-10-16 12:42:37, Robert Ho wrote:
> > > Recently, Redhat reported that nvml test suite failed on QEMU/KVM,
> > > more detailed info please refer to:
> > >    https://bugzilla.redhat.com/show_bug.cgi?id=1365721
> > > 
> [trim...]
> > > 
> > > In order to fix this bug, we make 'file->version' indicate the end address
> > > of current VMA
> > 
> > I guess you wanted to finish that sentence, right?
> > "
> > m_start will then look up a vma which with vma_start < last_vm_end and
> > moves on to the next vma if we found the same or an overlapping vma.
> > This will guarantee that we will not miss an exclusive vma but we can
> > still miss one if the previous vma was shrunk. This is acceptable
> > because guaranteeing "never miss a vma" is simply not feasible. User has
> > to cope with some inconsistencies if the file is not read in one go.
> > "
> 
> Yes, you're right. Sorry that I didn't complement that in v4.
> I see the patch is already moved to -mm tree (by you?) with the above
> complemented. So I'm not supposed to work a v5 patch, am I right?

Andrew took the patch and updated the changelog. So there doesn't seem
to be any reason for v5 just for to update changelog. Unless you want to
have a different wording of course.

[...]
> > I am not sure how the two above are helpful as the patch has been
> > reworked basically.
> > 
> I might be wrong, I thought the change log should honestly write each
> version's changes, although it indeed looks confusing if looks at this
> single version only.
> 
> So I learned from you now that change log shall only reflect the final
> adopted changes only, right?

well, I would keep the changelog if it was helpful - aka small changes
along the way between different submissions - but it is much less useful
when the solution changes completely or way to much. Reader would have
a very limited context to understand those changes without reading the
original email threads anyway.

Anyway, thanks for your persistence!
-- 
Michal Hocko
SUSE Labs

--
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>

  reply	other threads:[~2016-10-07  8:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01  4:42 Robert Ho
2016-10-01  4:42 ` [PATCH v4 2/2] Dcumentation/filesystems/proc.txt: Add more description for maps/smaps Robert Ho
2016-10-03 11:53   ` Michal Hocko
2016-10-03 11:52 ` [PATCH v4 1/2] mm, proc: Fix region lost in /proc/self/smaps Michal Hocko
2016-10-07  2:17   ` Robert Hu
2016-10-07  8:29     ` Michal Hocko [this message]
2016-10-03 15:51 ` Oleg Nesterov

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=20161007082952.GI18439@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --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=mtosatti@redhat.com \
    --cc=oleg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox