linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Rohland <hans-christoph.rohland@sap.com>
To: GOTO Masanori <gotom@debian.or.jp>
Cc: linux-kernel@vger.rutgers.edu, linux-MM@kvack.org
Subject: Re: [PATCH] shm fs v2 against 2.3.41
Date: 01 Feb 2000 13:46:25 +0100	[thread overview]
Message-ID: <qwwiu095bvi.fsf@sap.com> (raw)
In-Reply-To: GOTO Masanori's message of "Tue, 01 Feb 2000 19:07:20 +0900"

GOTO Masanori <gotom@debian.or.jp> writes:

> Calling shmget( key, size, shmflg ) with size = 0,
> I got an error EINVAL. The below patch fix it,
> please apply into 2.3.41+shmfs14 patch.
> 
> ---------------------
> --- linux-2.3.41_shmfs14/ipc/shm.c      Tue Feb  1 18:49:02 2000
> +++ linux-2.3.41_shmfs14_fixed/ipc/shm.c        Tue Feb  1 18:57:52 2000
> @@ -660,7 +660,7 @@
>                 return -EINVAL;
>         }
>  
> -       if (size < SHMMIN)
> +       if ((size != 0) && (size < SHMMIN))
>                 return -EINVAL;
>  
>         down(&shm_ids.sem);
> ---------------------

Yes, I stumbled over that yesterday evening also. I will put out a new
patch soon.

> And now I have a question:
> I guess almost all users have no shmpath (default: /var/shm),
> and they maybe make a dir and have to mount it.
> IMHO, it is better to change that sysv shared memory works
> samely, whenever shmfs is not mounted. Is it feasible, 
> or only my mistaken ?

This was my first attempt, but all the gurus opposed to that since
this needed some hacks to the VFS layer.

Since shmat, etc rely on the VFS functions, we have to mount the fs to
use these functions.

Greetings
		Christoph
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-02-01 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-30 15:12 Christoph Rohland
2000-02-01 10:07 ` GOTO Masanori
2000-02-01 12:46   ` Christoph Rohland [this message]
2000-02-02 14:24   ` Stephen C. Tweedie

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=qwwiu095bvi.fsf@sap.com \
    --to=hans-christoph.rohland@sap.com \
    --cc=gotom@debian.or.jp \
    --cc=linux-MM@kvack.org \
    --cc=linux-kernel@vger.rutgers.edu \
    /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