From: Willy Tarreau <w@1wt.eu>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
linux-kernel@vger.kernel.org, Al Viro <viro@ftp.linux.org.uk>
Subject: Re: Linux 2.4.33-rc1
Date: Mon, 19 Jun 2006 06:01:52 +0200 [thread overview]
Message-ID: <20060619040152.GB2678@1wt.eu> (raw)
In-Reply-To: <dmlb92lmehf2jufjuk8emmh63afqfmg5et@4ax.com>
On Mon, Jun 19, 2006 at 09:07:03AM +1000, Grant Coady wrote:
> On Mon, 19 Jun 2006 00:37:36 +0200, Willy Tarreau <w@1wt.eu> wrote:
>
> >Hi Grant,
> >
> >On Mon, Jun 19, 2006 at 08:25:06AM +1000, Grant Coady wrote:
> >> On Sun, 18 Jun 2006 10:37:18 -0300, Marcelo Tosatti <marcelo@kvack.org> wrote:
> >>
> >> >Can you please try the attached patch.
> >> >
> >> >Grab a reference to the victim inode before calling vfs_unlink() to avoid
> >> >it vanishing under us.
> >> >
> >> >diff --git a/fs/namei.c b/fs/namei.c
> >> >index 42cce98..7993283 100644
> >> >--- a/fs/namei.c
> >> >+++ b/fs/namei.c
> >> >@@ -1509,6 +1509,7 @@ asmlinkage long sys_unlink(const char *
> >> > char * name;
> >> > struct dentry *dentry;
> >> > struct nameidata nd;
> >> >+ struct inode *inode = NULL;
> >> >
> >> > name = getname(pathname);
> >> > if(IS_ERR(name))
> >> >@@ -1527,11 +1528,16 @@ asmlinkage long sys_unlink(const char *
> >> > /* Why not before? Because we want correct error value */
> >> > if (nd.last.name[nd.last.len])
> >> > goto slashes;
> >> >+ inode = dentry->d_inode;
> >> >+ if (inode)
> >> >+ atomic_inc(&inode->i_count);
> >> > error = vfs_unlink(nd.dentry->d_inode, dentry);
> >> > exit2:
> >> > dput(dentry);
> >> > }
> >
> >Could you add this line here, because your oops still looks like the NULL
> >is close to this area :
> >
> >+ printk(KERN_DEBUG "nd.dentry->d_inode = %p\n", nd.dentry->d_inode);
>
> It didn't get there for the segfault case, gets there for local file
> delete
>
> After:
> grant@sempro:~$ dmesg >dmesg
> grant@sempro:~$ rm dmesg
>
> Jun 19 08:49:17 sempro kernel: nd.dentry->d_inode = f73f4b80
>
> After:
> grant@sempro:~$ dmesg >/home/share/dmesg-test
> grant@sempro:~$ rm /home/share/dmesg-test
> Segmentation fault
>
> Nothing reported by debug or syslog, oops in messages.
Thanks. Then, could you send us your 'namei.o' file please ? Mine does
not produce the same content as yours and it makes it difficult to find
the exact position in the code.
Cheers,
Willy
next prev parent reply other threads:[~2006-06-19 4:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 18:14 Linux 2.4.33-rc1 Marcelo Tosatti
2006-06-16 22:21 ` Grant Coady
2006-06-16 22:38 ` Michal Piotrowski
2006-06-16 23:24 ` Grant Coady
2006-06-17 5:13 ` Willy Tarreau
2006-06-17 6:24 ` Grant Coady
2006-06-17 7:10 ` Willy Tarreau
2006-06-17 17:15 ` Need to format twice /dev/ramX with reiserfs to be able to mount it ? sebastien cabaniols
2006-06-17 18:14 ` Bernd Eckenfels
2006-06-17 18:37 ` sebastien cabaniols
2006-06-17 19:55 ` Linux 2.4.33-rc1 Marcelo Tosatti
2006-06-18 13:37 ` Marcelo Tosatti
2006-06-18 22:25 ` Grant Coady
2006-06-18 22:37 ` Willy Tarreau
2006-06-18 23:07 ` Grant Coady
2006-06-19 4:01 ` Willy Tarreau [this message]
2006-06-19 5:03 ` Grant Coady
2006-06-19 8:06 ` Willy Tarreau
2006-06-19 8:53 ` Grant Coady
2006-06-19 9:08 ` Willy Tarreau
2006-06-19 9:12 ` Grant Coady
2006-06-19 9:24 ` Willy Tarreau
2006-06-19 10:27 ` Grant Coady
2006-06-19 10:31 ` Willy Tarreau
2006-06-19 20:11 ` Grant Coady
2006-06-19 20:20 ` Willy Tarreau
2006-06-19 22:04 ` Marcelo Tosatti
2006-06-19 23:00 ` Willy Tarreau
2006-06-19 23:45 ` Marcelo Tosatti
2006-06-20 22:23 ` Willy Tarreau
2006-06-21 1:09 ` Grant Coady
2006-06-21 4:05 ` Willy Tarreau
2006-06-21 13:50 ` Marcelo Tosatti
2006-06-21 20:26 ` Willy Tarreau
2006-06-18 22:33 ` Grant Coady
2006-06-18 22:40 ` Willy Tarreau
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=20060619040152.GB2678@1wt.eu \
--to=w@1wt.eu \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.org \
--cc=viro@ftp.linux.org.uk \
/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