All of lore.kernel.org
 help / color / mirror / Atom feed
From: Korkakakis Nikos <korkakak@ceid.upatras.gr>
To: linux-kernel@vger.kernel.org, linux-newbie@vger.kernel.org
Subject: kmalloc returns twice  the same memory address?
Date: Tue, 30 Jun 2009 21:08:02 +0300	[thread overview]
Message-ID: <4A4A5482.3050108@ceid.upatras.gr> (raw)

Hi there all,

first of all I am writing a kernel module to handle some device using;
uname -a: Linux localhost 2.6.30-gentoo-r1 #1 SMP Sun Jun 28 02:52:23
EEST 2009 i686 AMD Phenom(tm) II X4 940 Processor AuthenticAMD GNU/Linux.
During  the init phase of the module I allocate some memory via
kmalloc() in the following manner;

    omm_dev_buffer = kmalloc(PAGE_SIZE, GFP_KERNEL | GFP_DMA | GFP_ATOMIC);
    if (!omm_dev_buffer) {
        return -ENOMEM;
    }
    clear_buffer (omm_dev_buffer, PAGE_SIZE);
    printk("omm_dev_init: kmalloc'ed omm_dev_buffer OK\n");
    omm_messages = kmalloc(PAGE_SIZE, GFP_KERNEL | GFP_DMA);
    printk ("dev_buff @ 0x%x messages @
0x%x\n",omm_dev_buffer,omm_messages);
    if (!omm_messages) {
        kfree(omm_dev_buffer); /* failing at this point means that the
other allocation succeeded */
        return -ENOMEM;
    }
    clear_buffer (omm_messages, PAGE_SIZE);


where clear_buffer is just a wrapper for memset. My problem is that the
two consecutive memory allocation operations return the same memory
space (both pointers point the same address). If I change the malloc'ed
size ie PAGE_SIZE*2 then the process works as expected. kzalloc behaves
the same way, while alloc_page with the same flags(i.e.
alloc_page(GFP_KERNEL | GFP_DMA | GFP_ATOMIC) ) return a different
memory space and works as expected.

What am I missing here?

Thank's in advance :D

Nikos
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

WARNING: multiple messages have this Message-ID (diff)
From: Korkakakis Nikos <korkakak@ceid.upatras.gr>
To: linux-kernel@vger.kernel.org, linux-newbie@vger.kernel.org
Subject: kmalloc returns twice  the same memory address?
Date: Tue, 30 Jun 2009 21:08:02 +0300	[thread overview]
Message-ID: <4A4A5482.3050108@ceid.upatras.gr> (raw)

Hi there all,

first of all I am writing a kernel module to handle some device using;
uname -a: Linux localhost 2.6.30-gentoo-r1 #1 SMP Sun Jun 28 02:52:23
EEST 2009 i686 AMD Phenom(tm) II X4 940 Processor AuthenticAMD GNU/Linux.
During  the init phase of the module I allocate some memory via
kmalloc() in the following manner;

    omm_dev_buffer = kmalloc(PAGE_SIZE, GFP_KERNEL | GFP_DMA | GFP_ATOMIC);
    if (!omm_dev_buffer) {
        return -ENOMEM;
    }
    clear_buffer (omm_dev_buffer, PAGE_SIZE);
    printk("omm_dev_init: kmalloc'ed omm_dev_buffer OK\n");
    omm_messages = kmalloc(PAGE_SIZE, GFP_KERNEL | GFP_DMA);
    printk ("dev_buff @ 0x%x messages @
0x%x\n",omm_dev_buffer,omm_messages);
    if (!omm_messages) {
        kfree(omm_dev_buffer); /* failing at this point means that the
other allocation succeeded */
        return -ENOMEM;
    }
    clear_buffer (omm_messages, PAGE_SIZE);


where clear_buffer is just a wrapper for memset. My problem is that the
two consecutive memory allocation operations return the same memory
space (both pointers point the same address). If I change the malloc'ed
size ie PAGE_SIZE*2 then the process works as expected. kzalloc behaves
the same way, while alloc_page with the same flags(i.e.
alloc_page(GFP_KERNEL | GFP_DMA | GFP_ATOMIC) ) return a different
memory space and works as expected.

What am I missing here?

Thank's in advance :D

Nikos

             reply	other threads:[~2009-06-30 18:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 18:08 Korkakakis Nikos [this message]
2009-06-30 18:08 ` kmalloc returns twice the same memory address? Korkakakis Nikos
2009-07-01  1:30 ` Robert Hancock
2009-07-01  1:30   ` Robert Hancock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A4A5482.3050108@ceid.upatras.gr \
    --to=korkakak@ceid.upatras.gr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.