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

Message-ID: <20070208202117.GA8429@infradead.org>
Date:	Thu, 8 Feb 2007 20:21:17 +0000
From:	Christoph Hellwig <hch@...radead.org>
To:	Mike Frysinger <vapier@...too.org>
Cc:	Christoph Hellwig <hch@...radead.org>, dushistov@...l.ru,
	linux-kernel@...r.kernel.org, sparc@...too.org
Subject: Re: [patch] export ufs_fs.h to userspace

On Thu, Feb 08, 2007 at 03:05:35PM -0500, Mike Frysinger wrote:
> > 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

Btw, if you're interesting in helping out in this area a little bit,
it would be nice if we could split up and move ufs_fs.h a little bit.
We should have an:

  fs/ufs/ufs.h for all driver internal declarations
  fs/ufs/ufs_layout.h that purely defines the layout can can be copied
                      directly into other tools that need the ufs layout
		      like silo
-
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/