All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Swanson <swansma@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Request: removal of fs/fs.h/super_block.u to enable partition locking
Date: Tue, 18 Sep 2001 22:14:42 -0400	[thread overview]
Message-ID: <3BA7FF92.D6477904@yahoo.com> (raw)

Why?

So I can write and distribute a GPL'd 'inuse' filesystem module
that essentially registers a partition as in-use.

I am writing an application that uses raw I/O and I need
some way of locking a partition. The only
way I know of (sortof) doing this is by registering a filesystem
for the partition so system utilities won't overwrite the partition
because they will see it is busy by examining /proc/partitions.

lockf()
on /dev/hda1 doesn't stop root from mounting the partition
as a swap partition or accidentally formatting it
even though the root partition was mounted with 'mand' to 
enable mandatory locking and a 'chmod 2660 /dev/hda1' was done 
to enable mandatory locking on the file.

I'm trying to look out for tired sys-admins who might 
destroy my application's partition not knowing
what a particular empty-looking partition is used for.

Thoughts?

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


             reply	other threads:[~2001-09-19  4:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-19  2:14 Mark Swanson [this message]
2001-09-19  6:00 ` Request: removal of fs/fs.h/super_block.u to enable partition locking Andreas Dilger
2001-09-19 19:28 ` Alan Cox
2001-09-19 19:50   ` Mark Swanson
2001-09-19 21:52     ` Request: removal of fs/fs.h/super_block.u to enable partition Alan Cox
2001-09-19 23:16       ` Andreas Dilger
2001-09-19 23:06     ` Request: removal of fs/fs.h/super_block.u to enable partition locking Andreas Dilger
2001-09-19 20:26   ` Andreas Dilger

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=3BA7FF92.D6477904@yahoo.com \
    --to=swansma@yahoo.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.