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-next>] [day] [month] [year] [list]
Date:	Thu, 21 Jun 2007 12:02:28 -0700
From:	Reza Roboubi <reza@...thdetails.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:	torvalds@...ux-foundation.org
Subject: O_DIRECT, fdatasync_area, mwrite

Linus Torvalds:
 > I suspect that this is about a few hundred lines of code (and a lot of
 > testing). And you can emulate O_DIRECT behavior with it, along with
 > splice (only for page-cache entities, though), and a lot of other
 > off-by-one uses.
( http://lwn.net/2002/0516/a/lt-async.php3 )

I have often read this message and wondered why no one has implemented 
it yet.  We would love to have such clean features instead of O_DIRECT. 
  At this very moment it's a bit hard for us to do this(given a 
prerequisites learning curve amongst other factors.)  We may at some 
point do it and I'd love to contribute.  What _are_ the issues with it, 
  and is there a technical reason it hasn't been implemented yet by anybody?

Further, is O_DIRECT to raw partition also unclean?

Thanks.

Reza.
-- 
Reza Roboubi
Chief Technical Officer
http://www.EarthDetails.com
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ