linux-kernel - [PATCH 0/4] resources: Add lookup

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:	Sat, 21 May 2011 21:39:12 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	linux-kernel@...r.kernel.org, sparclinux@...r.kernel.org,
	linux-m68k@...ts.linux-m68k.org
Subject: [PATCH 0/4] resources: Add lookup_resource()

The resource system is a nice existing subsystem to implement simple allocators
on top of.
Unfortunately, there's no official method to find an existing resource by a
resource start address, which is needed for a freeing function that just takes
the start address of the region to free.
        
Currently there are 3 users of the resource subsystem that implement this by
traversing the resource tree theirselves:
  - The Amiga Chip RAM allocator on m68k,
  - iomap()/iounmap() on sparc,
  - DMA allocation API on sparc.
They all lack locking of the resource tree, as resource_lock is static in
kernel/resource.c.

Hence this patchset adds lookup_resource() and converts the above users to it.

  [1/4] sparc: _sparc_find_resource() should check for exact matches
  [2/4] resources: Add lookup_resource()
  [3/4] m68k/amiga: Chip RAM - Use lookup_resource()
  [4/4] sparc: iounmap() and *_free_coherent() - Use lookup_resource()

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
--
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/