From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Drop cache has no effect?
Date: Thu, 31 Aug 2006 01:31:04 +0900 [thread overview]
Message-ID: <87ac5mtcc7.fsf@duaron.myhome.or.jp> (raw)
In-Reply-To: <Pine.LNX.4.61.0608300751330.9263@yvahk01.tjqt.qr> (Jan Engelhardt's message of "Wed, 30 Aug 2006 07:54:04 +0200 (MEST)")
Jan Engelhardt <jengelh@linux01.gwdg.de> writes:
>>>
>>> That's dirty area, vfat has one read-only bit only. Yes, I also think
>>> this is strange behaviour. But, I worry app is depending on the
>>> current behaviour, because this is pretty old behaviour.
>>>
>>> Umm.., do someone have any strong reason? I'll make patch at this
>>> weekend, and please test it in -mm tree for a bit long time...?
>>
>>It is pretty weird that permission bits on vfat can magically change in
>>response to memory pressure.
>
> Well, the same happened for procfs in the past (when one was able to chmod it,
> in current kernels it is forbidden.)
IIRC, at least 2.4 doesn't allow it, it's rather new.
> It seems the best thing ATM, no?
I also think it's good. But it wouldn't be good reason for breaking app...
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2006-08-30 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 12:53 Jan Engelhardt
2006-08-29 18:00 ` Andrew Morton
2006-08-29 19:21 ` Jan Engelhardt
2006-08-29 19:36 ` /proc/net/tcp information drop Jörg Hoffmann
2006-08-29 19:49 ` Drop cache has no effect? Andrew Morton
2006-08-30 1:08 ` OGAWA Hirofumi
2006-08-30 1:39 ` Andrew Morton
2006-08-30 5:54 ` Jan Engelhardt
2006-08-30 16:31 ` OGAWA Hirofumi [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=87ac5mtcc7.fsf@duaron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@osdl.org \
--cc=jengelh@linux01.gwdg.de \
--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
Powered by JetHome