linux-kernel - Re: [PATCH] bitmap: bitmap_parse takes a kernel buffer instead of a user buffer

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1479.10.24.212.168.1159888832.squirrel@linux.intel.com>
Date:	Tue, 3 Oct 2006 08:20:32 -0700 (PDT)
From:	inaky@...ux.intel.com
To:	"Reinette Chatre" <reinette.chatre@...ux.intel.com>
Cc:	"Andrew Morton" <akpm@...l.org>, linux-kernel@...r.kernel.org,
	"Inaky Perez-Gonzalez" <inaky@...ux.intel.com>
Subject: Re: [PATCH] bitmap: bitmap_parse takes a kernel buffer instead of 
     a user buffer


Hi Andrew

We are going to use this in the Linux UWB project; is it
possible/makes it sense to get it in?

> lib/bitmap.c:bitmap_parse() is a library function that received as input a
>  user buffer. This seemed to have originated from the way the write_proc
> function of the /proc filesystem operates.
>
> This function will be useful for other uses as well; for example, taking
> input  for /sysfs instead of /proc, so it was changed to accept kernel
> buffers. We have this use for the Linux UWB project, as part as the
> upcoming bandwidth allocator code.
>
> Only a few routines used this function and they were changed too.
>
> Signed-off-by: Reinette Chatre <reinette.chatre@...ux.intel.com>
Signed-off-by: Inaky Perez-Gonzalez <inaky@...ux.intel.com>

-- Inaky
-
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/