All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Donlan <bdonlan@gmail.com>
To: ranjith kannikara <ranjithkannikara@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Help to edit inode content
Date: Tue, 12 May 2009 11:56:03 -0400	[thread overview]
Message-ID: <3e8340490905120856w62c6c5cexa247937bf7e84002@mail.gmail.com> (raw)
In-Reply-To: <20aa8c370905120847j4b19175akbdcafc0db2004567@mail.gmail.com>

On Tue, May 12, 2009 at 11:47 AM, ranjith kannikara
<ranjithkannikara@gmail.com> wrote:
> Hi,
> I am a computer science engineering student. We have started a project
> to make an application to recover deleted files from an ext3
> filesystem. For that we have a doubt . Can we edit the inode content?
> ie the recovery will be robust if we could edit the inode contents and
> give the pointer address manually or through a code. The inode is
> being created in the kernel mode and is it possible to edit those
> contents if the code is allowed to have the kernel mode permissions..?

You'd probably be best off doing this in userspace, with the
filesystem unmounted.
Generally speaking, don't attempt to alter the filesystem from
userspace while it is mounted.

  reply	other threads:[~2009-05-12 15:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 15:47 Help to edit inode content ranjith kannikara
2009-05-12 15:56 ` Bryan Donlan [this message]
2009-05-12 16:02   ` ranjith kannikara
2009-05-12 16:13     ` Manish Katiyar
2009-05-12 16:13       ` Manish Katiyar
2009-05-12 20:03     ` Andreas Dilger
2009-05-13  4:11       ` ranjith kannikara
2009-05-13  4:11         ` ranjith kannikara
2009-05-13  4:14         ` Manish Katiyar
2009-05-13  4:14           ` Manish Katiyar
2009-05-13  4:23           ` ranjith kannikara
2009-05-13  4:23             ` ranjith kannikara
2009-05-13  4:28             ` Manish Katiyar
2009-05-13  4:28               ` Manish Katiyar
  -- strict thread matches above, loose matches on Subject: below --
2009-05-12 15:43 ranjith kannikara
2009-05-12 15:39 ranjith kannikara

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=3e8340490905120856w62c6c5cexa247937bf7e84002@mail.gmail.com \
    --to=bdonlan@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ranjithkannikara@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.