linux-ext4 - Re: kmalloc question.

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>] [day] [month] [year] [list]

Message-ID: <CAN2Q5rvDMM9U8dG=kDtuKHmRCXHuFJf+EOpDQsb_6zBOhhxyhA@mail.gmail.com>
Date:	Thu, 5 Jan 2012 14:05:56 +0530
From:	Ganesh Patil <patil.ganesh170@...il.com>
To:	Amir Goldstein <amir73il@...il.com>
Cc:	Theodore Tso <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: kmalloc question.

Thank you sir.

On 1/5/12, Amir Goldstein <amir73il@...il.com> wrote:
> Hi Ganesh,
>
> I am glad to learn that ext4 snapshots has become a "hot" research subject
> in Pune.
> However, I must say:
> 1. this is not the place to ask such basic questions.
> 2. your question shows that you are missing a lot of background before you
> can
> approach this kind of project.
>
> The answer in kernel memory (slab), BTW, which has nothing to do with root
> filesystem.
>
> Amir.
>
> On Wed, Jan 4, 2012 at 5:50 PM, Ganesh Patil
> <patil.ganesh170@...il.com>wrote:
>
>> Hello sir,
>>
>>         I am B.E(computer)student from Pune university (India) .my
>> final year project is "File system level snapshot in ext4 "  so have
>> to take snapshot of particular file system and place somewhere(on same
>> filesystem or on another filesystem) .in snapshot we are going to copy
>> only inode of file in to another inode. as inode size in particular
>> filesystem   is fixed so we cant get inode from filesystem(if
>> filesystem filled more than half) so finally we come to decision that
>> we will create one structure which has fields same as that of original
>> inode. so we will allocate memory dynamically using kmalloc
>> function.but we require that allocated memory cant be destroy till we
>> manually not destroy it.because of that I am asking from where kmalloc
>> allocates memory block(from current file system,or from kernel
>> space(root filesystem) or from RAM(heap area)).
>>
>> On 1/4/12, Theodore Tso <tytso@....edu> wrote:
>> >
>> > On Jan 4, 2012, at 9:22 AM, Ganesh Patil wrote:
>> >
>> >> where allocate kmalloc function memory?
>> >
>> > Sorry, I can't parse your question.
>> >
>> > -- Ted
>> >
>> >
>>
>>
>> --
>> Regards,
>> Ganesh Patil.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
>> the body of a message to majordomo@...r.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>


-- 
Regards,
Ganesh Patil.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html