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:45:29 +0100
From:	Markus Armbruster <armbru@...hat.com>
To:	"Jaya Kumar" <jayakumar.lkml@...il.com>
Cc:	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,
	akpm@...ux-foundation.org
Subject: Re: [PATCH 2/3] fbdev: Make deferred I/O work as advertized

"Jaya Kumar" <jayakumar.lkml@...il.com> writes:

> On Tue, Feb 26, 2008 at 9:45 AM, Markus Armbruster <armbru@...hat.com> wrote:
>>
>>  What about pushing the fb_defio fixes independently of any new
>>  fb_defio users?  If fb_defio was worth merging into Linus's tree, it
>>  should be worth fixing there, whether new users are in shape already
>>  or not.
>
> I think that Andrew's message is saying that there may be a race
> condition in the defio patch itself as opposed to the defio user
> patch.
>
> If there is no race condition or other problems, then I think it would
> make sense to merge the defio patch independent of metronomefb or
> other new patches that use defio.
>
> Thanks,
> jaya

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?
--
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/