| 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
| ||
|
Date: Thu, 15 Mar 2007 13:54:32 +0100 From: Jens Axboe <jens.axboe@...cle.com> To: Nick Piggin <npiggin@...e.de> Cc: Andrew Morton <akpm@...ux-foundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Memory Management List <linux-mm@...ck.org> Subject: Re: [patch 1/2] splice: dont steal On Thu, Mar 15 2007, Nick Piggin wrote: > On Thu, Mar 15, 2007 at 01:27:23PM +0100, Jens Axboe wrote: > > On Thu, Mar 15 2007, Nick Piggin wrote: > > > > > > We should be able to allow for it with the new a_ops API I'm working > > > on. > > > > "Should be" and in progress stuff, is it guarenteed to get there? > > Well considering that it is needed in order to solve 3 different deadlock > scenarios in the core write(2) path without taking a big performance hit, > I'd hope so ;) > > It isn't guaranteed, but I have only had positive feedback so far. Would > take a while to actually get merged, though. It's not that I don't believe you, I'm just a little reluctant to rip stuff out with a promise to fix it later when foo and bar are merged, since things like that have a tendency not to get done because they are forgotten :-) Do you have a test case for stealing failures? What I'm really asking is how critical is this? -- Jens Axboe - 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/
Powered by blists - more mailing lists