From: bfields@fieldses.org (J. Bruce Fields)
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-nfs@vger.kernel.org
Subject: sg_set_buf
Date: Tue, 18 Oct 2016 17:37:55 -0400 [thread overview]
Message-ID: <20161018213755.GA10777@fieldses.org> (raw)
The NFS code is using sg_set_buf to turn a bit of stack menory into a
scatterlist it can pass to the crypto code. That started BUG()ing as of
ac4e97abce9b "scatterlist: sg_set_buf() argument must be in linear
mapping".
Is that BUG() being overly strict, or is this something we should never
have been doing in the first place?
--b.
next reply other threads:[~2016-10-18 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 21:37 J. Bruce Fields [this message]
2016-10-20 10:22 ` sg_set_buf Christoph Hellwig
2016-10-20 13:20 ` sg_set_buf J. Bruce Fields
2016-10-20 13:31 ` sg_set_buf Christoph Hellwig
2016-10-20 21:42 ` sg_set_buf J. Bruce Fields
2016-10-21 12:26 ` sg_set_buf Christoph Hellwig
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=20161018213755.GA10777@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).