linux-kernel - kmalloc returns twice the same memory address?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 30 Jun 2009 21:08:02 +0300
From:	Korkakakis Nikos <korkakak@...d.upatras.gr>
To:	linux-kernel@...r.kernel.org, linux-newbie@...r.kernel.org
Subject: kmalloc returns twice  the same memory address?

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/