All of
 help / color / mirror / Atom feed
From: admin LI <>
Subject: How to disable address randomization ?
Date: Thu, 13 Jan 2022 22:01:30 +0100	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1518 bytes --]


I'm developing a kernel module for an ARM machine, while debugging I found
printed are all randomized and useless for debugging.

To prove I was not crazy I wrote this small program:

#include <linux/init.h>
#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/slab.h>

MODULE_DESCRIPTION("A simple example Linux module.");

static int __init example_init(void) {
    uint32_t a;
    uint32_t b;
    uint32_t c;
    uint8_t d[10];
    uint8_t *e;

    printk(KERN_INFO "Hello, World!\n");
    printk(KERN_INFO "&a %p\n",&a);
    printk(KERN_INFO "&b %p\n",&b);
    printk(KERN_INFO "&c %p\n",&c);
    printk(KERN_INFO "&d %p\n",d);
    printk(KERN_INFO "&d[0] %p\n",&d[0]);
    printk(KERN_INFO "&d[1] %p\n",&d[1]);

    e = kmalloc(10, GFP_KERNEL);
    printk(KERN_INFO "&e[0] %p\n",&e[0]);
    printk(KERN_INFO "&e[1] %p\n",&e[1]);


 return 0;

static void __exit example_exit(void) {
 printk(KERN_INFO "Goodbye, World!\n");

And it gave me this output:

Hello, World!
&a b3f9fa31
&b 27e1c68a
&c da50d287
&d 9f9aec2b
&d[0] 9f9aec2b
&d[1] cc627580
&e[0] 98b8c9eb
&e[1] 45f248f8

Then I tested on my debian host machine which gave me the same kind of
randomized addresses.

When I search randomization the only thing I found is KASLR which I don't
think is the same thing.

[-- Attachment #1.2: Type: text/html, Size: 2036 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

Kernelnewbies mailing list

             reply	other threads:[~2022-01-13 21:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 21:01 admin LI [this message]
2022-01-13 21:40 ` How to disable address randomization ? Valentin Vidić
2022-01-13 22:44 ` Jeffrey Walton
2022-01-13 23:54   ` Aruna Hewapathirane
2022-01-14  7:11     ` admin LI
2022-01-14  7:12   ` admin LI
2022-01-14  0:36 ` Chan Kim
2022-01-14  7:14   ` admin LI

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:

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

  git send-email \
    --in-reply-to='' \ \ \

* 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.