public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Alan Cox <laughing@shared-source.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.4-ac12
Date: Mon, 21 May 2001 23:33:03 +0200	[thread overview]
Message-ID: <20010521233303.A7310@werewolf.able.es> (raw)
In-Reply-To: <20010521201418.A2863@lightning.swansea.linux.org.uk>
In-Reply-To: <20010521201418.A2863@lightning.swansea.linux.org.uk>; from laughing@shared-source.org on Mon, May 21, 2001 at 21:14:18 +0200


On 05.21 Alan Cox wrote:
> 
> 	ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
> 
> 		 Intermediate diffs are available from
> 			http://www.bzimage.org
> 
> 
> 2.4.4-ac12
> o	Just tracking Linus 2.4.5pre4			
> 	- A chunk more merged with Linus
> 	- dropped out some oddments that are now
> 	  obsolete
> 

Two buglets:
- missing version bump from ac11 to ac12...
- missing change in binfmt_misc.c from lookup_one to lookup_one_len
	(is this the correct fix ? len is not already on Node...)

--- linux-2.4.4-ac12/fs/binfmt_misc.c.orig	Mon May 21 23:22:29 2001
+++ linux-2.4.4-ac12/fs/binfmt_misc.c	Mon May 21 23:24:53 2001
@@ -501,7 +501,7 @@
 
 	root = dget(sb->s_root);
 	down(&root->d_inode->i_sem);
-	dentry = lookup_one(e->name, root);
+	dentry = lookup_one_len(e->name, root, strlen(e->name));
 	err = PTR_ERR(dentry);
 	if (!IS_ERR(dentry)) {
 		down(&root->d_inode->i_zombie);

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Linux Mandrake release 8.1 (Cooker) for i586
Linux werewolf 2.4.4-ac11 #2 SMP Fri May 18 12:27:06 CEST 2001 i686


  reply	other threads:[~2001-05-21 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-21 19:14 Linux 2.4.4-ac12 Alan Cox
2001-05-21 21:33 ` J . A . Magallon [this message]
2001-05-22  5:53 ` Linux 2.4.4-ac12 -- fs/fs.o: In function `bm_register_write': undefined reference to `lookup_one' Miles Lane

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=20010521233303.A7310@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=laughing@shared-source.org \
    --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