From: Ingo Molnar <mingo@elte.hu>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [GIT] More NFS client fixes for 2.6.24-rc6
Date: Thu, 3 Jan 2008 10:30:48 +0100 [thread overview]
Message-ID: <20080103093048.GA16803@elte.hu> (raw)
In-Reply-To: <1199329417.28241.3.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
* Trond Myklebust <Trond.Myklebust@netapp.com> wrote:
> commit 53478daff2c8b494d2af1ede6611f166f81bc393
> Author: Trond Myklebust <Trond.Myklebust@netapp.com>
> Date: Wed Jan 2 13:28:57 2008 -0500
>
> NFS: Fix a possible Oops in fs/nfs/super.c
>
> Sigh... commit 4584f520e1f773082ef44ff4f8969a5d992b16ec (NFS: Fix NFS
> mountpoint crossing...) had a slight flaw: server can be NULL if sget()
> returned an existing superblock.
>
> Fix the fix by dereferencing s->s_fs_info.
>
> Also add in the same namespace Oops fix for NFSv4 in both the mountpoint
> crossing case, and the referral case.
>
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
shouldnt this commit have included the full credit of the bugfix:
http://bugzilla.kernel.org/show_bug.cgi?id=9647
------------>
Description From Adrian Bunk 2007-12-27 12:36
The Coverity checker spotted that commit
4584f520e1f773082ef44ff4f8969a5d992b16ec introduced the following NULL
dereference in 2.6.24-rc6:
<-- snip -->
if (s->s_fs_info != server) {
nfs_free_server(server);
server = NULL; <---------------
}
------- Comment #1 From Adrian Bunk 2007-12-27 12:37:42 -------
The NULL dereference is at the
server->nfs_client->rpc_ops->dir_inode_ops.
<--------------
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [GIT] More NFS client fixes for 2.6.24-rc6
Date: Thu, 3 Jan 2008 10:30:48 +0100 [thread overview]
Message-ID: <20080103093048.GA16803@elte.hu> (raw)
In-Reply-To: <1199329417.28241.3.camel@heimdal.trondhjem.org>
* Trond Myklebust <Trond.Myklebust@netapp.com> wrote:
> commit 53478daff2c8b494d2af1ede6611f166f81bc393
> Author: Trond Myklebust <Trond.Myklebust@netapp.com>
> Date: Wed Jan 2 13:28:57 2008 -0500
>
> NFS: Fix a possible Oops in fs/nfs/super.c
>
> Sigh... commit 4584f520e1f773082ef44ff4f8969a5d992b16ec (NFS: Fix NFS
> mountpoint crossing...) had a slight flaw: server can be NULL if sget()
> returned an existing superblock.
>
> Fix the fix by dereferencing s->s_fs_info.
>
> Also add in the same namespace Oops fix for NFSv4 in both the mountpoint
> crossing case, and the referral case.
>
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
shouldnt this commit have included the full credit of the bugfix:
http://bugzilla.kernel.org/show_bug.cgi?id=9647
------------>
Description From Adrian Bunk 2007-12-27 12:36
The Coverity checker spotted that commit
4584f520e1f773082ef44ff4f8969a5d992b16ec introduced the following NULL
dereference in 2.6.24-rc6:
<-- snip -->
if (s->s_fs_info != server) {
nfs_free_server(server);
server = NULL; <---------------
}
------- Comment #1 From Adrian Bunk 2007-12-27 12:37:42 -------
The NULL dereference is at the
server->nfs_client->rpc_ops->dir_inode_ops.
<--------------
Ingo
next prev parent reply other threads:[~2008-01-03 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 3:03 [GIT] More NFS client fixes for 2.6.24-rc6 Trond Myklebust
[not found] ` <1199329417.28241.3.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-03 9:30 ` Ingo Molnar [this message]
2008-01-03 9:30 ` Ingo Molnar
2008-01-03 14:45 ` Trond Myklebust
[not found] ` <1199371557.7357.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-03 18:20 ` Adrian Bunk
2008-01-03 18:20 ` Adrian Bunk
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=20080103093048.GA16803@elte.hu \
--to=mingo@elte.hu \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.