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]

Message-Id: <1170950377.8675.60.camel@laptopd505.fenrus.org>
Date:	Thu, 08 Feb 2007 16:59:37 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Mike Frysinger <vapier@...too.org>
Cc:	dushistov@...l.ru, linux-kernel@...r.kernel.org, sparc@...too.org
Subject: Re: [patch] export ufs_fs.h to userspace

On Thu, 2007-02-08 at 10:10 -0500, Mike Frysinger wrote:
> On Thursday 08 February 2007, Arjan van de Ven 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)
> 
> silo utilizes the structures and the random defines so that it can query UFS 
> filesystems directly

at which point arguably it should have it's own UFS header.
It's not using the UFS header to use as *kernel* interface!!

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

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