From: Maneesh Soni <maneesh@in.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@digeo.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Dipankar Sarma <dipankar@in.ibm.com>
Subject: [patch 0/3] dentry->d_count fixes
Date: Thu, 19 Jun 2003 18:39:43 +0530 [thread overview]
Message-ID: <20030619130943.GI1204@in.ibm.com> (raw)
Hi,
There are few races regarding the use of dentry->d_count
at various places as pointed by Trond. I have audited these and
made following patches for the places which I think are problemetic.
1. d_invalidate-fix.patch
- fixes race between d_invalidate & lockless d_lookup
2. nfs_unlink-d_count-fix.patch
- fixes race with nfs_unlink()
3. hpfs-d_count-fix.patch
- fixes race with hpfs_unlink()
Thanks,
Maneesh
--
Maneesh Soni
IBM Linux Technology Center,
IBM India Software Lab, Bangalore.
Phone: +91-80-5044999 email: maneesh@in.ibm.com
http://lse.sourceforge.net/
next reply other threads:[~2003-06-19 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 13:09 Maneesh Soni [this message]
2003-06-19 13:10 ` [patch 1/3] dentry->d_count fixes Maneesh Soni
2003-06-19 13:10 ` [patch 2/3] " Maneesh Soni
2003-06-19 13:11 ` [patch 3/3] " Maneesh Soni
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=20030619130943.GI1204@in.ibm.com \
--to=maneesh@in.ibm.com \
--cc=akpm@digeo.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox