linux-kernel - userspace firmware loader, vmap, and nommu

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, 6 Oct 2009 00:25:22 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	David Howells <dhowells@...hat.com>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	uclinux-dist-devel <uclinux-dist-devel@...ckfin.uclinux.org>
Subject: userspace firmware loader, vmap, and nommu

semi-recently (9 Apr 2009), the userspace firmware code was rewritten
to use vmap().  this causes problems for nommu systems as it isnt
possible to create a virtually contiguous map with physically
discontiguous pages.  the firmware loader used to work before this
change because it would handle the realloc steps itself (allocate
larger contiguous memory, copy over older data, release older memory)
and vmalloc() on nommu is simply kmalloc().

this could be handled transparently on nommu systems by moving this
scatter gathering of pages into vmap:
void *vmap(struct page **pages, unsigned int count, unsigned long
flags, pgprot_t prot)
{
    unsigned int i;
    void *new_map, *page_data;

    new_map = kmalloc(count << PAGE_SHIFT, GFP_KERNEL);
    if (!new_map)
        return NULL;

    for (i = 0; i < count; ++i) {
        page_data = kmap(pages[i]);
        memcpy(new_map + (i << PAGE_SHIFT), page_data, PAGE_SIZE);
        kunmap(page_data);
    }

    return new_map;
}
void vunmap(const void *addr)
{
    kfree(addr);
}

or we could add nommu-specific code to the firmware loader to not use
vmap().  how would you like to go David (Howells) ?

there is a possibility for the semi-common case of vmap-ing only one
page.  but i'm not familiar enough with the mm code to figure that
case out.
-mike
--
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/