From: Christoph Hellwig <hch@infradead.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-embedded@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chris Brandt <Chris.Brandt@renesas.com>
Subject: Re: [PATCH 1/5] cramfs: direct memory access support
Date: Sat, 12 Aug 2017 00:49:27 -0700 [thread overview]
Message-ID: <20170812074927.GA8703@infradead.org> (raw)
In-Reply-To: <20170811192252.19062-2-nicolas.pitre@linaro.org>
Direct physical memory access in a file system is never safe.
Please make sure this goes through struct dax_operations.
next prev parent reply other threads:[~2017-08-12 7:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 19:22 [PATCH 0/5] cramfs refresh for embedded usage Nicolas Pitre
2017-08-11 19:22 ` [PATCH 1/5] cramfs: direct memory access support Nicolas Pitre
2017-08-12 7:49 ` Christoph Hellwig [this message]
2017-08-14 2:29 ` Nicolas Pitre
2017-08-11 19:22 ` [PATCH 2/5] cramfs: make cramfs_physmem usable as root fs Nicolas Pitre
2017-08-11 19:22 ` [PATCH 3/5] cramfs: implement uncompressed and arbitrary data block positioning Nicolas Pitre
2017-08-11 19:22 ` [PATCH 4/5] cramfs: add mmap support Nicolas Pitre
2017-08-11 19:22 ` [PATCH 5/5] cramfs: rehabilitate it Nicolas Pitre
2017-08-14 17:11 ` [PATCH 0/5] cramfs refresh for embedded usage Chris Brandt
2017-08-14 17:31 ` Nicolas Pitre
2017-08-14 18:01 ` Chris Brandt
2017-08-14 18:17 ` Nicolas Pitre
2017-08-14 18:37 ` Chris Brandt
2017-08-15 4:10 ` Nicolas Pitre
2017-08-15 11:00 ` Chris Brandt
2017-08-16 5:10 ` Nicolas Pitre
2017-08-16 11:08 ` Chris Brandt
2017-08-16 14:29 ` Nicolas Pitre
2017-08-16 15:12 ` Chris Brandt
2017-08-17 1:17 ` Nicolas Pitre
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=20170812074927.GA8703@infradead.org \
--to=hch@infradead.org \
--cc=Chris.Brandt@renesas.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®