linux-kernel - Re: 2.6.19 -mm merge plans

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]

Message-Id: <1158788521.1198.19.camel@dyn9047017100.beaverton.ibm.com>
Date:	Wed, 20 Sep 2006 14:42:01 -0700
From:	Badari Pulavarty <pbadari@...il.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19 -mm merge plans

On Wed, 2006-09-20 at 13:54 -0700, Andrew Morton wrote:

Sorry, I didn't get back to this earlier. I have been chasing
one more ext2 & ext3 regression (this time with random reads).
Anyway ..

> add-address_space_operationsbatch_write.patch
> add-address_space_operationsbatch_write-fix.patch
> pass-io-size-to-batch_write-address-space-operation.patch
> 
>  These add a new address_space operation.  For reiser4, with potential for
>  use by other filesystems.
> 
>  Problem is, 2.6.18 has a significant writev() performace regression on NFS
>  and probably on other filesystems.  Because 2.6.18 does
>  prepare_write/commit_write for each iovec segment.  We want to go back to
>  copying mulitple iovec segments within a single prepare_write/commit_write.
> 
>  Plus there's still the possible deadlock in our standard write() function
>  (thw thing which fault_in_pages_readable() tries to prevent).
> 
>  All of this should be fixed.  


What needs to be fixed here ?

Thanks,
Badari

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