linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vineet Joglekar" <vintya@excite.com>
To: linux-kernel@vger.kernel.org
Cc: linux-c-programming@vger.kernel.org
Subject: Problem in accessing executable files
Date: Tue,  1 Feb 2005 08:58:57 -0500 (EST)	[thread overview]
Message-ID: <20050201135857.154ED1E491@xprdmailfe25.nwk.excite.com> (raw)


Hi all,



I am trying to add some cryptographic functionality to ext2 file system for my masters project. I am working with kernel 2.4.21



since the routines do_generic_file_read and do_generic_file_write are used in reading and writing, I am decrypting and encrypting the data in the resp. functions. This is working fine for regular data files. If I try to copy / execute executable files, I am getting segmentation fault. In kernel messages, I see same functions (read and write) getting called for the executables also. If I comment encrypt/decrypt functions, its working fine.



Now since it is working for regular text files, I suppose there is not a problem in my encrypt/decrypt routines, then what might be going wrong?



Thanks and regards,



Vineet

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!

             reply	other threads:[~2005-02-01 13:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01 13:58 Vineet Joglekar [this message]
2005-02-01 15:37 ` Problem in accessing executable files John T. Williams
  -- strict thread matches above, loose matches on Subject: below --
2005-02-06 22:41 Vineet Joglekar
2005-02-07 18:31 ` Glynn Clements
2005-02-08  2:33 Vineet Joglekar
2005-02-09  0:14 Vineet Joglekar
2005-02-09  0:21 ` Al Viro

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=20050201135857.154ED1E491@xprdmailfe25.nwk.excite.com \
    --to=vintya@excite.com \
    --cc=linux-c-programming@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).