* [PATCH/RFC] minix filesystem update to V3. Error comment.
@ 2006-05-02 7:24 Daniel Aragonés
0 siblings, 0 replies; only message in thread
From: Daniel Aragonés @ 2006-05-02 7:24 UTC (permalink / raw)
To: Joshua Hudson; +Cc: Jiri Slaby, linux-kernel, Andrew Morton
Joshua wrote:
> Is this the error about variable might not be initalized?
> What happends in the code if you just initalize to NULL?
Hi all,
No, is not this kind of error. The error message complaints about not beeing able to reference the contents of a pointer if you previously not allocate with kmalloc a location for it. Nothig has to
bee initialized because the target and contents already exists.
Nothing happens if I initialize to NULL. An exception happens if I later free it with kfree instead of setting it to NULL.
Be aware that all this happens within functions included by bitops.h.
Regards,
Daniel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-05-02 7:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-02 7:24 [PATCH/RFC] minix filesystem update to V3. Error comment Daniel Aragonés
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.