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

On 5/1/06, Jiri Slaby <[email protected]> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Aragonés napsal(a):
> 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.
Ok, which error?

Is this the error about variable might not be initalized?
What happends in the code if you just initalize to NULL?
-
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/

---

• 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]>
  • Re: [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: Jiri Slaby <[email protected]>

• Prev by Date: Re: [PATCH] likely cleanup: revert unlikely in ll_back_merge_fn
• Next by Date: Re: + drivers-scsi-use-array_size-macro.patch added to -mm tree
• 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]