From: "Zurk Tech" <zurktech@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Weird subtle kernel problem (maybe kernel, maybe driver, maybe ???)
Date: Thu, 13 Dec 2007 19:09:05 -0500 [thread overview]
Message-ID: <2ed59cbb0712131609r38d736cay4facc07748122cdb@mail.gmail.com> (raw)
heres what i did on two different machines -
both had vanilla 2.6.23 kernels from kernel.org, running debian etch,
all updates.
first patched with truecrypt driver. second machne loaded with LUKS
and kernel crypto enabled.
both machines create 2GB encrypted file and mounted under a directory
after formatting with mkfs.vfat.
copy files, do diffs etc and test em. both are fine reading/writing
files to encrypted space, mount and unmount fine.
i then load the jdk on both and simple java read write file program.
works great.
then i do a new File("test.txt").exists() - test.txt doesnt actually exist.
truecrypt machine return false as expected. the linux kernel LUKS
crypto machine returns true.
also moved from 32 to 64 bits -- same result. tried with different
jdks from 1.4 to 1.6 latest. same result.
i dont get it. and i dont even know how to begin to test it. is this a
kernel bug ? app bug ? driver bug ? jdk bug ? vfat bug ?
anyone help diagnose it ?
-Z-
reply other threads:[~2007-12-14 0:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ed59cbb0712131609r38d736cay4facc07748122cdb@mail.gmail.com \
--to=zurktech@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®