public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chiaki <ishikawa@yk.rim.or.jp>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org, mru@inprovide.com, anton@samba.org
Subject: Re: Configuration system bug? : tmpfs listing in /proc/filesystems when TMPFS was not configured!?
Date: Sun, 07 Nov 2004 15:00:20 +0900	[thread overview]
Message-ID: <418DB9F4.8030301@yk.rim.or.jp> (raw)
In-Reply-To: <Pine.LNX.4.44.0411070436080.12803-100000@localhost.localdomain>

Hugh Dickins wrote:

> On Sun, 7 Nov 2004, Chiaki wrote:
> 
>>Should not this line be ifdef'ed out???
>>That is, should we modify the line like this?
>>
>>#ifdef CONFIG_TMPFS
>>	error = register_filesystem(&tmpfs_fs_type);
>>#endif
> 
> 
> I'd be more inclined to register under a different
> name than "tmpfs" in the !CONFIG_TMPFS case.

Something like "tMpfs" might be a good idea to
show the strange setting :-)

> 
> But as I said in my earlier reply to you (which you should have
> received before you sent this?), it's been like this ever since
> 2.4.4 when "tmpfs" and CONFIG_TMPFS came into being, so I don't
> see why we need to change it now.

Thank you for your previous e-mail.
I didn't know it reached my computer since my mozilla e-mail
filtering mitakingly classified your kind response into
an unexpected folder. I searched after reading the above paragraph
and found your previous e-mail.

> The real 2.4.9 error is fixed by the patch below that I sent then:
> does that solve your problems?

YES!

With the original 2.6.9, the mount didn't complain at all, and
then I got bizarre behavir afterward and udev script and booting
stopped at that point.

But wih your patch, now mount fails.
So now it is a matter of fixing udev script to
take care of the case of failing tmpfs mounting.
I will re-open the debian bugzilla entry concerning this
so that Debian udev package and possibly an upstream package
can be fixed.



tmpfs mount failure example: (I had created /tmp/t-dir.)

duron:/home/ishikawa# mount -n -o size=1m,mode=0755 -t tmpfs none /tmp/t-dir
mount: wrong fs type, bad option, bad superblock on none,
        or too many mounted file systems
duron:/home/ishikawa#


> Hugh
> 
> --- 2.6.9/mm/shmem.c	2004-10-18 22:56:29.000000000 +0100
> +++ linux/mm/shmem.c	2004-11-06 21:04:41.743173040 +0000
> @@ -1904,6 +1904,8 @@ static int shmem_fill_super(struct super
>  		sbinfo->max_inodes = inodes;
>  		sbinfo->free_inodes = inodes;
>  	}
> +#else
> +	sb->s_flags |= MS_NOUSER;
>  #endif
>  
>  	sb->s_maxbytes = SHMEM_MAX_BYTES;
> 
> 
> 


Thank you very much!



-- 
int main(void){int j=2003;/*(c)2003 cishikawa. */
char t[] ="<CI> @abcdefghijklmnopqrstuvwxyz.,\n\"";
char *i ="g>qtCIuqivb,gCwe\np@.ietCIuqi\"tqkvv is>dnamz";
while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof t-1),
(putchar(t[j])));return 0;}/* under GPL */

      reply	other threads:[~2004-11-07  6:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 17:50 Configuration system bug? : tmpfs listing in /proc/filesystems when TMPFS was not configured!? Chiaki
2004-11-06 19:04 ` [PATCH] " Måns Rullgård
2004-11-06 21:09 ` Hugh Dickins
2004-11-07  1:31 ` Chiaki
2004-11-07  2:05   ` Chiaki
2004-11-07  2:12   ` Chiaki
2004-11-07  4:49     ` Hugh Dickins
2004-11-07  6:00       ` Chiaki [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=418DB9F4.8030301@yk.rim.or.jp \
    --to=ishikawa@yk.rim.or.jp \
    --cc=anton@samba.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@inprovide.com \
    /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