mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Jan Marek <linux@hazard.jcu.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.3-mm1][PROBLEM] Apache cannot start
Date: Thu, 19 Feb 2004 08:10:40 -0800	[thread overview]
Message-ID: <20040219081040.6c56b801.rddunlap@osdl.org> (raw)
In-Reply-To: <20040219131221.GA1328@hazard.jcu.cz>

On Thu, 19 Feb 2004 14:12:21 +0100 Jan Marek <linux@hazard.jcu.cz> wrote:

| Hallo lkml,
| 
| I have problem with kernel 2.6.3-mm1: apache cannot start. Some last
| lines from strace output:
| 
| 3299  shmget(IPC_PRIVATE, 737284, IPC_CREAT|0600) = 393216
| 3299  shmat(393216, 0, 0)               = -1 EINVAL (Invalid argument)
| 3299  time(NULL)                        = 1077193406
| 3299  write(15, "[Thu Feb 19 13:23:26 2004] [emer"..., 69) = 69
| 3299  shmctl(393216, IPC_64|IPC_RMID, 0) = 0
| 3299  munmap(0x40018000, 4096)          = 0
| 3299  exit_group(2)                     = ?
| 
| I think, that problem is in the calling shmat function?
| 
| My last kernel was 2.6.2-mm1 and here apache went without problems...


Patch from Andrew is below.

--
~Randy



diff -puN ipc/shm.c~add-syscalls_h-shmat-fix ipc/shm.c
--- 25/ipc/shm.c~add-syscalls_h-shmat-fix	2004-02-18 01:22:41.000000000 -0800
+++ 25-akpm/ipc/shm.c	2004-02-18 01:22:41.000000000 -0800
@@ -635,7 +635,7 @@ out:
  * "raddr" thing points to kernel space, and there has to be a wrapper around
  * this.
  */
-long sys_shmat(int shmid, char __user *shmaddr, int shmflg, ulong *raddr)
+asmlinkage long sys_shmat(int shmid, char __user *shmaddr, int shmflg, ulong *raddr)
 {
 	struct shmid_kernel *shp;
 	unsigned long addr;

      reply	other threads:[~2004-02-19 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 13:12 Jan Marek
2004-02-19 16:10 ` Randy.Dunlap [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=20040219081040.6c56b801.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@hazard.jcu.cz \
    /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®