linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: j@falooley.org (Jason Lunz)
Cc: linux-kernel@vger.kernel.org, almesber@lrc.di.epfl.ch
Subject: Re: RFC: from FIBMAP to FIONDEV
Date: Thu, 14 Jun 2001 18:16:36 +0100 (BST)	[thread overview]
Message-ID: <E15AajU-0004wp-00@the-village.bc.nu> (raw)
In-Reply-To: <20010614100354.A2129@orr.falooley.org> from "Jason Lunz" at Jun 14, 2001 10:03:54 AM

> I'm looking for a way to do FIBMAP on linux 2.4 without being root, and
> I learned from the archive that it's restricted for security reasons,
> and that it's obsolete anyway.  I found this discussion about a
> replacement called FIONDEV:

FIBMAP can be handled per fs by auditing the code paths. First job would be
to push the security check into each fs, then audit the fs's and then change
them. But its really a 2.5 job since any third party fs might spontaneously
become insecure oitherwise

      reply	other threads:[~2001-06-14 17:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-14 14:03 RFC: from FIBMAP to FIONDEV Jason Lunz
2001-06-14 17:16 ` Alan Cox [this message]

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=E15AajU-0004wp-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=almesber@lrc.di.epfl.ch \
    --cc=j@falooley.org \
    --cc=linux-kernel@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).