From: "Vineet Joglekar" <vintya@excite.com>
To: glynn@gclements.plus.com
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Problem in accessing executable files
Date: Mon, 7 Feb 2005 21:33:26 -0500 (EST) [thread overview]
Message-ID: <20050208023326.4D8A5109EF7@xprdmailfe1.nwk.excite.com> (raw)
Hi Glynn,
Thanks a lot for the reply. I will try that too.
I forgot to mention 1 thing, that I had put printk() in the do_generic_file_read function to see if it is getting executed, and I saw the printed message for executables too. Thats why I assumed that these functions do get executed while accessing executable files. Is it someting like other mmap functions get executed before calling regular read?
Thanks and regards,
Vineet
--- On Mon 02/07, Glynn Clements < glynn@gclements.plus.com > wrote:
From: Glynn Clements [mailto: glynn@gclements.plus.com]
To: vintya@excite.com
Cc: jtwilliams@vt.edu, linux-c-programming@vger.kernel.org
Date: Mon, 7 Feb 2005 18:31:24 +0000
Subject: Re: Problem in accessing executable files
<br>Vineet Joglekar wrote:<br><br>> Thanks for suggesting the single / few bytes encryption test. I tried<br>> doing that, but in vain. Maybe I am going wrong somewhere else.<br><br>I'm pretty sure that mmap'ed access doesn't go through<br>do_generic_file_read().<br><br>Executable files (programs and shared libraries) are normally mmap'ed<br>rather than read, which would explain why you have problems with<br>executable files.<br><br>Try writing a test program which reads the contents of a file using<br>mmap() rather than read(). If my assumption is correct, the decryption<br>code will be bypassed, so you will get the encrypted data.<br><br>-- <br>Glynn Clements <glynn@gclements.plus.com><br>
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
next reply other threads:[~2005-02-08 2:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 2:33 Vineet Joglekar [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 0:14 Problem in accessing executable files Vineet Joglekar
2005-02-09 0:21 ` Al Viro
2005-02-06 22:41 Vineet Joglekar
2005-02-07 18:31 ` Glynn Clements
2005-02-01 13:58 Vineet Joglekar
2005-02-01 15:37 ` John T. Williams
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=20050208023326.4D8A5109EF7@xprdmailfe1.nwk.excite.com \
--to=vintya@excite.com \
--cc=glynn@gclements.plus.com \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).