| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-id: <1366887697-24627-2-git-send-email-jaegeuk.kim@samsung.com> Date: Thu, 25 Apr 2013 20:01:36 +0900 From: Jaegeuk Kim <jaegeuk.kim@...sung.com> To: unlisted-recipients:; (no To-header on input) Cc: Jaegeuk Kim <jaegeuk.kim@...sung.com>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net Subject: [PATCH 2/3] f2fs: add a tracepoint on f2fs_new_inode This can help when debugging the free nid allocation flows. Signed-off-by: Jaegeuk Kim <jaegeuk.kim@...sung.com> --- fs/f2fs/namei.c | 3 ++- include/trace/events/f2fs.h | 7 +++++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c index c57fd18..4aa26e5 100644 --- a/fs/f2fs/namei.c +++ b/fs/f2fs/namei.c @@ -63,7 +63,7 @@ static struct inode *f2fs_new_inode(struct inode *dir, umode_t mode) nid_free = true; goto out; } - + trace_f2fs_new_inode(inode, 0); mark_inode_dirty(inode); return inode; @@ -71,6 +71,7 @@ out: clear_nlink(inode); unlock_new_inode(inode); fail: + trace_f2fs_new_inode(inode, err); iput(inode); if (nid_free) alloc_nid_failed(sbi, ino); diff --git a/include/trace/events/f2fs.h b/include/trace/events/f2fs.h index b2b2f72..52ae548 100644 --- a/include/trace/events/f2fs.h +++ b/include/trace/events/f2fs.h @@ -197,6 +197,13 @@ DEFINE_EVENT(f2fs__inode, f2fs_evict_inode, TP_ARGS(inode) ); +DEFINE_EVENT(f2fs__inode_exit, f2fs_new_inode, + + TP_PROTO(struct inode *inode, int ret), + + TP_ARGS(inode, ret) +); + TRACE_EVENT(f2fs_unlink_enter, TP_PROTO(struct inode *dir, struct dentry *dentry), -- 1.8.1.3.566.gaa39828 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists