Hi!
> Was just wondering if the _var_ in kfree(_var_) could be set to NULL after its freed. It may solve
> the problem of accessing some freed memory as the kernel will crash since _var_ was set to NULL.
>
> Does this make sense? If yes, then how about renaming kfree to something else and providing a
> kfree macro that would do the following:
>
> #define kfree(x) do { \
> new_kfree(x); \
> x = NULL; \
> } while(0)
>
> There might be other better ways too.
No, that would be very confusing. Otoh having
KFREE() do kfree() and assignment might be acceptable.
Pavel
--
Thanks for all the (sleeping) penguins.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
