From: Greg KH <greg@kroah.com>
To: Michael Halcrow <mhalcrow@us.ibm.com>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org,
sandeen@redhat.com, akpm@linux-foundation.org,
dustin.kirkland@gmail.com, pjssilva@ime.usp.br
Subject: Re: [stable] [PATCH] eCryptfs: Allocate up to two scatterlists for crypto ops on keys
Date: Fri, 14 Nov 2008 08:58:07 -0800 [thread overview]
Message-ID: <20081114165807.GA20656@kroah.com> (raw)
In-Reply-To: <20081114164053.GC6624@halcrowt61p.austin.ibm.com>
On Fri, Nov 14, 2008 at 10:40:53AM -0600, Michael Halcrow wrote:
> I have received some reports of out-of-memory errors on some older AMD
> architectures. These errors are what I would expect to see if
> crypt_stat->key were split between two separate pages. eCryptfs should
> not assume that any of the memory sent through virt_to_scatterlist()
> is all contained in a single page, and so this patch allocates two
> scatterlist structs instead of one when processing keys. I have
> received confirmation from one person affected by this bug that this
> patch resolves the issue for him, and so I am submitting it for
> inclusion in a future stable release.
Is this already in Linus's tree? If so, do you have the git commit id
for it?
If not, we can't take it into a stable kernel until that happens. To
get patches automatically added to the stable tree, when they get added
to Linus's tree, just add:
Cc: stable <stable@kernel.org>
to the signed-off-by: area of the patch and it will get automatically
routed to us.
thanks,
greg k-h
next prev parent reply other threads:[~2008-11-14 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 16:40 [PATCH] eCryptfs: Allocate up to two scatterlists for crypto ops on keys Michael Halcrow
2008-11-14 16:49 ` Leon Woestenberg
2008-11-18 22:31 ` Michael Halcrow
2008-11-14 16:58 ` Greg KH [this message]
2008-11-17 20:27 ` Michael Halcrow
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=20081114165807.GA20656@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=dustin.kirkland@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=pjssilva@ime.usp.br \
--cc=sandeen@redhat.com \
--cc=stable@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