From: Mel Gorman <mel@csn.ul.ie>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
linux-kernel mlist <linux-kernel@vger.kernel.org>
Subject: Re: Patch "mm: vmscan: forcibly scan highmem if there are too many buffer_heads pinning highmem" has been added to the 3.3-stable tree
Date: Thu, 29 Mar 2012 10:31:13 +0100 [thread overview]
Message-ID: <20120329093113.GR1007@csn.ul.ie> (raw)
In-Reply-To: <20120329053639.GA7603@pcnci2.linuxbox.cz>
On Thu, Mar 29, 2012 at 07:36:39AM +0200, Nikola Ciprich wrote:
> Hi,
>
> I'm not 100% sure, but I think this one could go to 3.0.x as well, am I right?
> If it's so, could I try to provide backport? (it't doesn't apply cleanly).
If you want to try a backport go right ahead. There is an indirect dependency
on [2bcf8879: mm: take pagevecs off reclaim stack] which is not suitable
for backporting to -stable but handling that should be easy.
> Mel, would You care to review then? Or do You plan to send Your own backport?
>
I had not planned my own backport because the type of bug made it a low
priority for me (copying NTFS with small block size on 32 bit X86 with 16G
of RAM). If you backport it, I'll review the result. I will be at LSF/MM next
week so I might be a bit slow to respond but I'll get around to it. Thanks.
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2012-03-29 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13325234973644@kroah.org>
2012-03-29 5:36 ` Patch "mm: vmscan: forcibly scan highmem if there are too many buffer_heads pinning highmem" has been added to the 3.3-stable tree Nikola Ciprich
2012-03-29 9:31 ` Mel Gorman [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=20120329093113.GR1007@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
--cc=stable@vger.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