linux-kernel - Re: [PATCH 2/3] fbdev: Make deferred I/O work as advertized

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 19 Mar 2008 11:37:45 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Jaya Kumar" <jayakumar.lkml@...il.com>
Cc:	"Markus Armbruster" <armbru@...hat.com>,
	linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org,
	xen-devel@...ts.xensource.com,
	linux-fbdev-devel@...ts.sourceforge.net, adaplas@....net,
	linux-input@...r.kernel.org, dmitry.torokhov@...il.com
Subject: Re: [PATCH 2/3] fbdev: Make deferred I/O work as advertized

On Wed, 19 Mar 2008 19:24:25 +0800 "Jaya Kumar" <jayakumar.lkml@...il.com> wrote:

> On Wed, Mar 19, 2008 at 6:45 PM, Markus Armbruster <armbru@...hat.com> wrote:
> >
> >  Any progress on this?
> >
> >  Considering that fb_defio is utterly broken without the fix (writing
> >  the frame buffer makes the VM endlessly invoke vm_ops.page_mkwrite()),
> >  wouldn't it make sense to merge the fix even if it still has issues?
> >
> 
> Yes, Andrew has merged the fix into -mm. I see it in mmotm
> 
> http://userweb.kernel.org/~akpm/mmotm/broken-out/fbdev-defio-and-metronomefb-v4.patch
> 

Do we need some of all of that patch in 2.6.25?  I wasn't aware of such a
need.

If the drivers/video/fb_defio.c hunk of that patch fixes something then I'd
be inclined to merge the whole thing - adding a new driver won't hurt
anyone.
--
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/