From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: linux-xfs@vger.kernel.org, linux-nvdimm@lists.01.org,
linux-api@vger.kernel.org, Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org
Subject: Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
Date: Tue, 2 Oct 2018 07:52:06 -0700 [thread overview]
Message-ID: <20181002145206.GA10903@infradead.org> (raw)
In-Reply-To: <20181002144412.GC4963@linux-x5ow.site>
On Tue, Oct 02, 2018 at 04:44:13PM +0200, Johannes Thumshirn wrote:
> On Tue, Oct 02, 2018 at 07:37:13AM -0700, Christoph Hellwig wrote:
> > No, it should not. DAX is an implementation detail thay may change
> > or go away at any time.
>
> Well we had an issue with an application checking for dax, this is how
> we landed here in the first place.
So what exacty is that "DAX" they are querying about (and no, I'm not
joking, nor being philosophical).
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-10-02 14:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 10:05 Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps Jan Kara
2018-10-02 10:50 ` Michal Hocko
2018-10-02 13:32 ` Jan Kara
2018-10-02 12:10 ` Johannes Thumshirn
2018-10-02 14:20 ` Johannes Thumshirn
2018-10-02 14:45 ` Christoph Hellwig
2018-10-02 15:01 ` Johannes Thumshirn
2018-10-02 15:06 ` Christoph Hellwig
2018-10-04 10:09 ` Johannes Thumshirn
2018-10-05 6:25 ` Christoph Hellwig
2018-10-05 6:35 ` Johannes Thumshirn
2018-10-06 1:17 ` Dan Williams
2018-10-14 15:47 ` Dan Williams
2018-10-17 20:01 ` Dan Williams
2018-10-18 17:43 ` Jan Kara
2018-10-18 19:10 ` Dan Williams
2018-10-19 3:01 ` Dave Chinner
2018-10-02 14:29 ` Jan Kara
2018-10-02 14:37 ` Christoph Hellwig
2018-10-02 14:44 ` Johannes Thumshirn
2018-10-02 14:52 ` Christoph Hellwig [this message]
2018-10-02 15:31 ` Jan Kara
2018-10-02 20:18 ` Dan Williams
2018-10-03 12:50 ` Jan Kara
2018-10-03 14:38 ` Dan Williams
2018-10-03 15:06 ` Jan Kara
2018-10-03 15:13 ` Dan Williams
2018-10-03 16:44 ` Jan Kara
2018-10-03 21:13 ` Dan Williams
2018-10-04 10:04 ` Johannes Thumshirn
2018-10-02 15:07 ` Jan Kara
2018-10-17 20:23 ` Jeff Moyer
2018-10-18 0:25 ` Dave Chinner
2018-10-18 14:55 ` Jan Kara
2018-10-19 0:43 ` Dave Chinner
2018-10-30 6:30 ` Dan Williams
2018-10-30 22:49 ` Dave Chinner
2018-10-30 22:59 ` Dan Williams
2018-10-31 5:59 ` y-goto
2018-11-01 23:00 ` Dave Chinner
2018-11-02 1:43 ` y-goto
2018-10-18 21:05 ` Jeff Moyer
2018-10-09 19:43 ` Jeff Moyer
2018-10-16 8:25 ` Jan Kara
2018-10-16 12:35 ` Jeff Moyer
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=20181002145206.GA10903@infradead.org \
--to=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jthumshirn@suse.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.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;
as well as URLs for NNTP newsgroup(s).