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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200702081505.36513.vapier@gentoo.org>
Date:	Thu, 8 Feb 2007 15:05:35 -0500
From:	Mike Frysinger <vapier@...too.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	dushistov@...l.ru, linux-kernel@...r.kernel.org, sparc@...too.org
Subject: Re: [patch] export ufs_fs.h to userspace

On Thursday 08 February 2007, Christoph Hellwig wrote:
> On Thu, Feb 08, 2007 at 02:46:16AM -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
>
> We should only export kernel interfaces and ufs_fs.h isn't one.  silo
> wants it because it defines the ufs format - but the linux structs for
> that can and do change, e.g. adding unions when we add support for the
> gazillion+1st ufs format variant.  silo should just grab a copy of it
> that it's happy with it and update it when it needs to support another
> format variant (which I think is a rather theoretical issue as silo
> only supports the solaris/sparc format IIR)

seems logical to mean, thanks for the response
-mike

Content of type "application/pgp-signature" skipped