From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: tadeusz.struk@intel.com, linux-kernel@vger.kernel.org,
smueller@chronox.de, mmarek@suse.com, arnd@arndb.de,
andrew.zaborowski@intel.com,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH v2] lib/mpi: Fix kernel unaligned access in mpi_write_to_sgl
Date: Tue, 3 May 2016 06:19:15 -0400 [thread overview]
Message-ID: <20160503101915.GI23757@oracle.com> (raw)
In-Reply-To: <20160503081230.GA17085@gondor.apana.org.au>
On (05/03/16 16:12), Herbert Xu wrote:
>
> Sorry, but your patch doesn't apply against the current tree at all.
> Please rebase it if it is still needed.
Hello,
I had based my patch off of net-next, which is where I do my work.
I'd be happy to rebase it on the "current tree",
but given that mpicoder.c does not have an entry in MAINTAINERS,
please clarify what you mean by "current tree" in this case.
do you mean
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
or
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
or
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
(which are the three possible candidates I can see in MAINTAINERS).
It would be nice to get this bug fixed, since the fix is fairly
obvious, and the nuisance factor from the generated "unaligned
access" messages on the impacted non-intel platforms is quite high,
thanks,
--Sowmini
next prev parent reply other threads:[~2016-05-03 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160427174338.GA15460@oracle.com>
[not found] ` <20160428010117.GA5262@gondor.apana.org.au>
[not found] ` <20160428010827.GE15460@oracle.com>
2016-05-03 8:12 ` [PATCH v2] lib/mpi: Fix kernel unaligned access in mpi_write_to_sgl Herbert Xu
2016-05-03 10:19 ` Sowmini Varadhan [this message]
2016-05-04 2:32 ` Herbert Xu
2016-05-04 11:05 ` Sowmini Varadhan
2016-04-27 17:43 Sowmini Varadhan
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=20160503101915.GI23757@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=andrew.zaborowski@intel.com \
--cc=arnd@arndb.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=smueller@chronox.de \
--cc=tadeusz.struk@intel.com \
/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).