From: Pavel Machek <pavel@suse.cz>
To: David Feuer <David_Feuer@brown.edu>, linux-kernel@vger.kernel.org
Subject: Re: swapoff weird
Date: Fri, 15 Dec 2000 19:32:17 +0100 [thread overview]
Message-ID: <20001215193217.A3960@bug.ucw.cz> (raw)
In-Reply-To: <4.3.2.7.2.20001209174435.00aaf310@postoffice.brown.edu> <20001209222427.A1542@bug.ucw.cz> <4.3.2.7.2.20001209174435.00aaf310@postoffice.brown.edu> <20001210015623.V6567@cadcamlab.org> <4.3.2.7.2.20001210040635.00b63340@postoffice.brown.edu>
In-Reply-To: <4.3.2.7.2.20001210040635.00b63340@postoffice.brown.edu>; from David Feuer on Sun, Dec 10, 2000 at 04:10:15AM -0500
Hi!
> >[David Feuer]
> > > Perhaps it would be good to put a check in unlink to make sure that
> > > this is not the last link to a swapfile.
> >
> >Much better to add code to /sbin/swapon and /sbin/swapoff to set and
> >clear immutable bit. Sure it only works on ext2 but how far do you
> >want to take this thing?
>
> In a private email, linux@horizon.com wrote:
>
> >No; we should add some more magic-symlink /proc entries, like
> >/proc/<pid>/fd/<n> for swap files. Then they can be accessed
> >by swapoff even if they're deleted.
>
> Seems like a good idea to me...
We could make them opened by kswapd.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-15 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-09 21:24 swapoff weird Pavel Machek
2000-12-09 21:41 ` Rik van Riel
2000-12-09 22:06 ` Pavel Machek
2000-12-09 22:41 ` David Ford
2000-12-09 22:46 ` David Feuer
2000-12-10 7:56 ` Peter Samuelson
2000-12-10 9:10 ` David Feuer
2000-12-15 18:32 ` Pavel Machek [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=20001215193217.A3960@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=David_Feuer@brown.edu \
--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