From: "Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu>
To: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL -mm] Unionfs updates
Date: Sun, 4 Mar 2007 21:16:44 -0500 [thread overview]
Message-ID: <11730610174005-git-send-email-jsipek@cs.sunysb.edu> (raw)
The following patches (also available though the git tree) address a number
of code issues with Unionfs. (Sorry if you got duplicates, I forgot to CC
fsdevel.)
You can pull from 'master' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jsipek/unionfs.git
to receive the following:
Erez Zadok (6):
fs/unionfs: Fix a memory leak & null pointer dereference
fs/unionfs/: Fix a memory leak in unionfs_read_super
fs/unionfs/: Fix copyup_deleted_file dentry leak
fs/unionfs/: mntput in __cleanup_dentry
fs/unionfs/: Fix dentry leak in copyup_named_dentry
fs/unionfs/: Fix unlocking in error paths
Josef 'Jeff' Sipek (7):
fs/unionfs/: Don't grab dentry private data mutex in unionfs_d_release
fs/unionfs/: Several small cleanups in unionfs_interpose
fs/unionfs/: Rename unionfs_d_revalidate_wrap
fs/unionfs/: Remove alloc_filldir_node
fs/unionfs/: Use SEEK_{SET,CUR} instead of hardcoded values
fs/unionfs/: Check return value of d_path
fs/unionfs/: Miscellaneous coding style fixes
fs/unionfs/commonfops.c | 22 ++++++++++++++++++----
fs/unionfs/copyup.c | 17 +++++++++++++----
fs/unionfs/dentry.c | 15 ++++-----------
fs/unionfs/dirfops.c | 6 +++---
fs/unionfs/lookup.c | 11 +++++++++--
fs/unionfs/main.c | 18 ++++++------------
fs/unionfs/rdstate.c | 8 +-------
fs/unionfs/super.c | 8 ++++++--
fs/unionfs/union.h | 2 +-
9 files changed, 61 insertions(+), 46 deletions(-)
Josef 'Jeff' Sipek.
jsipek@cs.sunysb.edu
next reply other threads:[~2007-03-05 2:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 2:16 Josef 'Jeff' Sipek [this message]
2007-03-05 2:16 ` [PATCH 01/13] fs/unionfs: Fix a memory leak & null pointer dereference Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 02/13] fs/unionfs/: Fix a memory leak in unionfs_read_super Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 03/13] fs/unionfs/: Don't grab dentry private data mutex in unionfs_d_release Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 04/13] fs/unionfs/: Several small cleanups in unionfs_interpose Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 05/13] fs/unionfs/: Rename unionfs_d_revalidate_wrap Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 06/13] fs/unionfs/: Remove alloc_filldir_node Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 07/13] fs/unionfs/: Use SEEK_{SET,CUR} instead of hardcoded values Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 08/13] fs/unionfs/: Check return value of d_path Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 09/13] fs/unionfs/: Miscellaneous coding style fixes Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 10/13] fs/unionfs/: Fix copyup_deleted_file dentry leak Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 11/13] fs/unionfs/: mntput in __cleanup_dentry Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 12/13] fs/unionfs/: Fix dentry leak in copyup_named_dentry Josef 'Jeff' Sipek
2007-03-05 2:16 ` [PATCH 13/13] fs/unionfs/: Fix unlocking in error paths Josef 'Jeff' Sipek
-- strict thread matches above, loose matches on Subject: below --
2007-05-05 20:18 [GIT PULL -mm] Unionfs updates Josef 'Jeff' Sipek
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=11730610174005-git-send-email-jsipek@cs.sunysb.edu \
--to=jsipek@cs.sunysb.edu \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).