mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Drop cache has no effect?
Date: Tue, 29 Aug 2006 18:39:02 -0700	[thread overview]
Message-ID: <20060829183902.be1356b6.akpm@osdl.org> (raw)
In-Reply-To: <87k64rxc6g.fsf@duaron.myhome.or.jp>

On Wed, 30 Aug 2006 10:08:39 +0900
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:

> Andrew Morton <akpm@osdl.org> writes:
> 
> > That would be a vfat problem - the changed permission bits weren't written
> > back to disk, so when you re-read them from disk (or, more likely, from
> > blockdev pagecache) they came back with the original values.
> >
> > Does vfat even have the ability to store the seven bits?  Don't think so? 
> > If not, permitting the user to change them in icache but not being to write
> > them out to permanent store seems rather bad behaviour.
> 
> 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.

But no, I'm not really advocating any changes in this area - I don't recall
any complaints (surprised) and the chances are that if we changed it
(ie: not permit the inode to accept changes which cannot be stored on disk)
then someone's app would break.

otoh, it is pretty bad behaviour...

  reply	other threads:[~2006-08-30  1:39 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 [this message]
2006-08-30  5:54       ` Jan Engelhardt
2006-08-30 16:31         ` OGAWA Hirofumi

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=20060829183902.be1356b6.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --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

all inboxes | Powered by JetHome®