LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Alexey Dobriyan" <adobriyan@gmail.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: "Mike Frysinger" <vapier@gentoo.org>,
	dushistov@mail.ru, linux-kernel@vger.kernel.org,
	sparc@gentoo.org
Subject: Re: [patch] export ufs_fs.h to userspace
Date: Thu, 8 Feb 2007 14:33:22 +0300	[thread overview]
Message-ID: <b6fcc0a0702080333q12bd7493y227ef92e5273a664@mail.gmail.com> (raw)
In-Reply-To: <1170930819.8675.36.camel@laptopd505.fenrus.org>

On 2/8/07, Arjan van de Ven <arjan@infradead.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.

  reply	other threads:[~2007-02-08 11:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08  7:46 Mike Frysinger
2007-02-08 10:33 ` Arjan van de Ven
2007-02-08 11:33   ` Alexey Dobriyan [this message]
2007-02-08 15:10   ` Mike Frysinger
2007-02-08 15:59     ` Arjan van de Ven
2007-02-08 16:12       ` Mike Frysinger
2007-02-08 20:02 ` Christoph Hellwig
2007-02-08 20:05   ` Mike Frysinger
2007-02-08 20:21     ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b6fcc0a0702080333q12bd7493y227ef92e5273a664@mail.gmail.com \
    --to=adobriyan@gmail.com \
    --cc=arjan@infradead.org \
    --cc=dushistov@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparc@gentoo.org \
    --cc=vapier@gentoo.org \
    --subject='Re: [patch] export ufs_fs.h to userspace' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).