From: Christoph Hellwig <hch@infradead.org>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: Eric Biggers <ebiggers@google.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-crypto@vger.kernel.org, tytso@mit.edu, jaegeuk@kernel.org,
richard@nod.at, luto@kernel.org
Subject: Re: [PATCH 1/2] fscrypto: don't use on-stack buffer for filename encryption
Date: Mon, 7 Nov 2016 07:44:44 -0800 [thread overview]
Message-ID: <20161107154444.GA13796@infradead.org> (raw)
In-Reply-To: <20161105151349.e5ap547uno3hfit7@kmo-pixel>
On Sat, Nov 05, 2016 at 07:13:49AM -0800, Kent Overstreet wrote:
> Vmalloc memory does have struct pages - you just need to use vmalloc_to_page()
> instead of virt_to_page. Look at drivers/md/bcache/util.c bch_bio_map() if you
> want an example.
That example seems to be clearly broken on virtually index caches
due to the lack of flush_kernel_vmap_range and
invalidate_kernel_vmap_range calls.
next prev parent reply other threads:[~2016-11-07 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 22:03 [PATCH 1/2] fscrypto: don't use on-stack buffer for filename encryption Eric Biggers
2016-11-03 22:03 ` [PATCH 2/2] fscrypto: don't use on-stack buffer for key derivation Eric Biggers
2016-11-07 13:22 ` Richard Weinberger
2016-11-15 16:47 ` Theodore Ts'o
2016-11-15 18:53 ` Eric Biggers
2016-11-05 15:13 ` [PATCH 1/2] fscrypto: don't use on-stack buffer for filename encryption Kent Overstreet
2016-11-05 15:13 ` Kent Overstreet
2016-11-07 5:00 ` Andy Lutomirski
2016-11-07 15:44 ` Christoph Hellwig [this message]
2016-11-07 13:15 ` Richard Weinberger
2016-11-15 16:46 ` Theodore Ts'o
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=20161107154444.GA13796@infradead.org \
--to=hch@infradead.org \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
/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.