From: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Cannot allocate memory error on mount
Date: Fri, 27 Aug 2010 07:17:18 -0400 [thread overview]
Message-ID: <20100827071718.6c21ab44@corrin.poochiereds.net> (raw)
In-Reply-To: <4C775A03.8010507-l3A5Bk7waGM@public.gmane.org>
On Fri, 27 Aug 2010 11:54:03 +0530
Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org> wrote:
> On 08/26/2010 09:55 PM, Steve French wrote:
> > This is a good one to go upstream soon - if others critical to go
> > upstream soon let me know.
>
> Do we need to Cc -stable as well? I don't feel strongly that we should
> include this fix. However, unrelated memory allocation errors during
> mount in supported kernels sounds more than annoying..
>
> Thoughts?
>
It doesn't seem like stable material to me. It's an annoyance, but not a
security or stability fix as far as I can see...
--
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
prev parent reply other threads:[~2010-08-27 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 20:26 Cannot allocate memory error on mount joe hefner
[not found] ` <514808.54527.qm-21+BQsVhpP+B9c0Qi4KiSs0jms80CZx+QQ4Iyu8u01E@public.gmane.org>
2010-08-26 9:16 ` Suresh Jayaraman
[not found] ` <4C7630D9.7060203-l3A5Bk7waGM@public.gmane.org>
2010-08-26 12:23 ` Jeff Layton
[not found] ` <20100826082305.1594ec4e-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>
2010-08-26 16:25 ` Steve French
[not found] ` <AANLkTi=qnTFUcnu-uS8NGTkjYUhO-hHstargorpJ8yZ9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-27 6:24 ` Suresh Jayaraman
[not found] ` <4C775A03.8010507-l3A5Bk7waGM@public.gmane.org>
2010-08-27 11:17 ` Jeff Layton [this message]
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=20100827071718.6c21ab44@corrin.poochiereds.net \
--to=jlayton-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sjayaraman-l3A5Bk7waGM@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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