linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Anthony Yznaga <anthony.yznaga@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	adobriyan@gmail.com, akpm@linux-foundation.org, vbabka@suse.cz,
	sfr@canb.auug.org.au, kirill.shutemov@linux.intel.com,
	rppt@linux.vnet.ibm.com, mhocko@suse.com,
	alexander.h.duyck@linux.intel.com, hannes@cmpxchg.org,
	miles.chen@mediatek.com, n-horiguchi@ah.jp.nec.com
Subject: Re: [PATCH] /proc/kpagecount: return 0 for special pages that are never mapped
Date: Wed, 5 Dec 2018 20:26:31 -0800	[thread overview]
Message-ID: <20181206042631.GA24603@bombadil.infradead.org> (raw)
In-Reply-To: <d9fa0325-690d-47cc-fc49-2606855f6a4f@oracle.com>

On Wed, Dec 05, 2018 at 04:44:15PM -0800, Anthony Yznaga wrote:
> On 12/05/2018 11:44 AM, Matthew Wilcox wrote:
> > Nobody seems terribly interested in mapcount overflows.  I got no response
> > to https://lkml.org/lkml/2018/3/2/991
> 
> Okay.� Thanks for the background.
> 
> How about this, then:

Acked-by: Matthew Wilcox <willy@infradead.org>

  reply	other threads:[~2018-12-06  4:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 22:45 [PATCH] /proc/kpagecount: return 0 for special pages that are never mapped Anthony Yznaga
2018-12-05  0:48 ` Matthew Wilcox
2018-12-05  1:18   ` anthony.yznaga
2018-12-05  1:25     ` Matthew Wilcox
2018-12-05 19:40       ` Anthony Yznaga
2018-12-05 19:44         ` Matthew Wilcox
2018-12-06  0:44           ` Anthony Yznaga
2018-12-06  4:26             ` Matthew Wilcox [this message]
2018-12-06  6:07               ` Anthony Yznaga
2018-12-08  0:27                 ` Andrew Morton
2018-12-05  8:28   ` David Hildenbrand

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=20181206042631.GA24603@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.h.duyck@linux.intel.com \
    --cc=anthony.yznaga@oracle.com \
    --cc=hannes@cmpxchg.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=miles.chen@mediatek.com \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=vbabka@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).