[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201203311619.38921.a.miskiewicz@gmail.com>
Date: Sat, 31 Mar 2012 16:19:38 +0200
From: Arkadiusz Miśkiewicz <a.miskiewicz@...il.com>
To: Vasiliy Kulikov <segoon@...nwall.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, Valdis.Kletnieks@...edu,
linux-kernel@...r.kernel.org, Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: [PATCH] proc: reset mount options after the last procfs umount
On Saturday 31 of March 2012, Vasiliy Kulikov wrote:
> On Mon, Mar 26, 2012 at 15:37 -0700, Andrew Morton wrote:
> > On Sun, 25 Mar 2012 18:23:16 -0400
> >
> > Valdis.Kletnieks@...edu wrote:
> > > Yes, it may be what the code actually *does*, but it certainly violates
> > > the Principle of Least Surprise...
> >
> > It surprises me ;) I never noticed that before.
> >
> > It does seem pretty insane. I wonder how much downstream damage would
> > result from fixing it.
>
> Resetting options on each mount is implemented in the following patch.
"after all procs are umounted". For me such way is fine but still can suprise
people.
Anyway - what's the problem with implementing support for separate options for
each mount point?
> I wonder whether anybody will try to do such parallel type of things
> in reality (IOW, is it OK to leave this race?)
I mount multiple procs when using linux-vserver but these are currently not
happening in parallel (but could be).
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
--
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/
Powered by blists - more mailing lists