* [RFC]fs/ramfs/inode.c
@ 2011-09-30 15:02 harryxiyou
0 siblings, 0 replies; only message in thread
From: harryxiyou @ 2011-09-30 15:02 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-fsdevel, linux-kernel, Andrew Morton
Hi all,
When i read ramfs's inode file fs/ramfs/inode.c. I just see the following codes
and get some confusions.
[......]
static void ramfs_kill_sb(struct super_block *sb)
{
kfree(sb->s_fs_info);
kill_litter_super(sb);
}
[.....]
If we can really free the sb->s_fs_info successfully everytime? Ok, you may say
kfree returns no value. But how we can guarantee it can be freed
right. And The same
problem with the function kill_litter_super(sb). We also have some
other functions, which
i have the same confusions. I have searched the relevant codes about
kfree() with the tool
ctags and cscope, but i get so many relevant codes. I can not
distinguish which is the right
one. I think if we can not let the os stop, we just printk the
relevant error logs and make os
run as usual.
Thanks
Harry Wei
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-09-30 15:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-30 15:02 [RFC]fs/ramfs/inode.c harryxiyou
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.