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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sl9z3u5k.fsf@duaron.myhome.or.jp>
Date:	Tue, 15 May 2007 07:41:27 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Hubertus Grobbel <hubertus@...bbel.net>
Cc:	Linux List <linux-kernel@...r.kernel.org>
Subject: Re: O_DIRECT for FAT

Hubertus Grobbel <hubertus@...bbel.net> writes:

> I found out, that the option O_DIRECT for opening a file on a fat-
> filesystem successfully completes. But reading and writing to that
> file leads to EINVAL errors (using kernel 2.6.18).

EINVAL may be meaning the memory alignment which you passed to syscall
is wrong.

> Do you see a way to solve my problem by any workaround? Is O_DIRECT
> support for fat-fs feasible in future?

The fatfs is supporting O_DIRECT for read, for write it's partially
supporting (can't extend file size).
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
-
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