public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Isaac Claymore <clay@exavio.com.cn>
To: linux-kernel@vger.kernel.org
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: 2.6.0 kernel panic
Date: Wed, 31 Dec 2003 11:53:25 +0800	[thread overview]
Message-ID: <20031231035325.GA15138@exavio.com.cn> (raw)
In-Reply-To: <Pine.LNX.4.58.0312292238390.4176@home.osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

On Mon, Dec 29, 2003 at 10:42:06PM -0800, Linus Torvalds wrote:
> 
> 
> On Mon, 29 Dec 2003, Murray J. Root wrote:
> > On Sat, Dec 27, 2003 at 09:07:59PM -0500, Murray J. Root wrote:
> > > P4 2GHz
> > > ASUS P4S533 mainboard
> > > 1G PC2700 RAM
> > > GF2 GTS video using nv driver
> > > 2.6.0 compiled with gcc 3.3.2
> > > 
> > > At boot kernel gets:
> > >    INIT: cannot execute "/etc/rc.d/rc.sysinit"
> > > then panic.
> > > 
> > > Same configuration for 2.6.0-test11 and earlier works fine.
> > > 
> > 
> > To answer myself, I did a diff between 2.6.0-test11 and 2.6.0. Found this:
> 
> Sounds like one of the partitions that has the executable script loader is
> mounted with "noexec". 
> 
> On most systems, /etc/rc.d/rc.sysinit is a bash script, and explicitly
> points to /bin/bash. Check "ldd /bin/bash", and verify that all the
> libraries (and /bin itself, of course) are mounted on executable
> filesystems.
> 
> That would be a bug that 2.6.0 uncovers. 

I've noticed that 2.4.23 lacks this additional check, and included a
patch against it.

Marcelo, does this trivial stuff look good enough to be applied?


-Isaac

> 
> 		Linus
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 

Regards, Isaac
()  ascii ribbon campaign - against html e-mail
/\                        - against microsoft attachments

[-- Attachment #2: mmap.do_mmap_pgoff.diff --]
[-- Type: text/plain, Size: 670 bytes --]

--- mmap.c	2003-12-05 09:39:09.000000000 +0800
+++ mmap.c.execproto	2003-12-31 11:25:12.000000000 +0800
@@ -17,6 +17,7 @@
 
 #include <asm/uaccess.h>
 #include <asm/pgalloc.h>
+#include <linux/mount.h>
 
 /*
  * WARNING: the debugging will use recursive algorithms so never enable this
@@ -400,8 +401,13 @@ unsigned long do_mmap_pgoff(struct file 
 	int error;
 	rb_node_t ** rb_link, * rb_parent;
 
-	if (file && (!file->f_op || !file->f_op->mmap))
-		return -ENODEV;
+	if (file) {
+		if (!file->f_op || !file->f_op->mmap)
+			return -ENODEV;
+
+		if ((prot & PROT_EXEC) && (file->f_vfsmnt->mnt_flags & MNT_NOEXEC))
+			return -EPERM;
+	}
 
 	if (!len)
 		return addr;

      parent reply	other threads:[~2003-12-31  3:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-28  2:07 2.6.0 kernel panic Murray J. Root
2003-12-28 10:58 ` Han Boetes
2003-12-30  3:30 ` Murray J. Root
2003-12-30  6:42   ` Linus Torvalds
2003-12-30  7:07     ` Murray J. Root
2003-12-31  3:53     ` Isaac Claymore [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=20031231035325.GA15138@exavio.com.cn \
    --to=clay@exavio.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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