From: akpm@linux-foundation.org
To: hirofumi@mail.parknet.co.jp, marvin24@gmx.de,
trond.myklebust@fys.uio.no, mm-commits@vger.kernel.org
Subject: [merged] nfs-fix-oops-in-nfs_rename.patch removed from -mm tree
Date: Fri, 08 Jan 2010 13:02:30 -0800 [thread overview]
Message-ID: <201001082102.o08L2UMY013937@imap1.linux-foundation.org> (raw)
The patch titled
nfs: fix oops in nfs_rename()
has been removed from the -mm tree. Its filename was
nfs-fix-oops-in-nfs_rename.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: nfs: fix oops in nfs_rename()
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Recent change is missing to update "rehash". With that change, it will
become the cause of adding dentry to hash twice.
This explains the reason of Oops (dereference the freed dentry in
__d_lookup()) on my machine.
Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Reported-by: Marvin <marvin24@gmx.de>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/nfs/dir.c | 1 +
1 file changed, 1 insertion(+)
diff -puN fs/nfs/dir.c~nfs-fix-oops-in-nfs_rename fs/nfs/dir.c
--- a/fs/nfs/dir.c~nfs-fix-oops-in-nfs_rename
+++ a/fs/nfs/dir.c
@@ -1615,6 +1615,7 @@ static int nfs_rename(struct inode *old_
goto out;
new_dentry = dentry;
+ rehash = NULL;
new_inode = NULL;
}
}
_
Patches currently in -mm which might be from hirofumi@mail.parknet.co.jp are
linux-next.patch
rtc_cmos-convert-shutdown-to-new-pnp_driver-shutdown.patch
tpm_infineon-fix-suspend-resume-handler-for-pnp_driver.patch
reply other threads:[~2010-01-08 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201001082102.o08L2UMY013937@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=marvin24@gmx.de \
--cc=mm-commits@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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.