Re: [PATCH/RFC] minix filesystem update to V3 diffed to 2.6.17-rc3

Hi Andrew,

Well, I don't know how to solve it. If I don't allocate with kmalloc, the compiler stops with error. If I free memory with kfree instead of setting offset = NULL, an exception is produced.

Sorry.

Daniel
-
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/

Follow-Ups:
- Re: [PATCH/RFC] minix filesystem update to V3 diffed to 2.6.17-rc3
  - From: Jiri Slaby <[email protected]>

References:
- [PATCH/RFC] minix filesystem update to V3 diffed to 2.6.17-rc3
  - From: Daniel Aragonés <[email protected]>
- Re: [PATCH/RFC] minix filesystem update to V3 diffed to 2.6.17-rc3
  - From: Andrew Morton <[email protected]>

Prev by Date: Re: 2.6.17-rc2-mm1
Next by Date: Re: [PATCH 8 of 13] ipath - fix a number of RC protocol bugs
Previous by thread: Re: [PATCH/RFC] minix filesystem update to V3 diffed to 2.6.17-rc3
Next by thread: Re: [PATCH/RFC] minix filesystem update to V3 diffed to 2.6.17-rc3
Index(es):
- Date
- Thread

[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]