linux-kernel - Re: [patch] export ufs

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]

Date:	Thu, 8 Feb 2007 14:33:22 +0300
From:	"Alexey Dobriyan" <adobriyan@...il.com>
To:	"Arjan van de Ven" <arjan@...radead.org>
Cc:	"Mike Frysinger" <vapier@...too.org>, dushistov@...l.ru,
	linux-kernel@...r.kernel.org, sparc@...too.org
Subject: Re: [patch] export ufs_fs.h to userspace

On 2/8/07, Arjan van de Ven <arjan@...radead.org> wrote:
> On Thu, 2007-02-08 at 02:46 -0500, Mike Frysinger wrote:
> > was ufs_fs.h purposefully not exported to userspace or did it just slip
> > through the cracks ?  assuming the latter scenario, the attached patch
> > touches up the relationship between ufs_fs.h and its sub headers (like
> > ufs_fs_sb.h) so that we can export it ... the silo bootloader takes
> advantage
> > of this header for example
>
>
> are you sure it actually uses anything from this header, and not just
> assumes the magic number to be there??
> (also.. I kind of would think it reasonable for things with their own
> UFS fs reader to have their own header)

ufs_fs.h certainly has things which certain types of userspace
programs could use:
on-disk layouts of UFS(2) inodes, cylinder groups, ... So it should be exported.

However, NAK patch in this form until all kernel internal things would
dissapear from
exported header: struct ufs_buffer_head, ufs_sb_private_info. Probably something
else, I haven't looked closely.
-
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/