linux-kernel - 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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120329093113.GR1007@csn.ul.ie>
Date:	Thu, 29 Mar 2012 10:31:13 +0100
From:	Mel Gorman <mel@....ul.ie>
To:	Nikola Ciprich <nikola.ciprich@...uxbox.cz>
Cc:	gregkh@...uxfoundation.org, stable@...r.kernel.org,
	linux-kernel mlist <linux-kernel@...r.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

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/