From: Josh Boyer <jwboyer@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
davej@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] lockdep: Add helper function for dir vs file i_mutex annotation
Date: Thu, 25 Aug 2011 07:25:33 -0400 [thread overview]
Message-ID: <20110825112533.GN2270@zod.bos.redhat.com> (raw)
In-Reply-To: <1314262683.12180.1.camel@twins>
On Thu, Aug 25, 2011 at 10:58:03AM +0200, Peter Zijlstra wrote:
> On Wed, 2011-08-24 at 21:37 -0400, Josh Boyer wrote:
>
> > and make it work. Given that the helper function calls
> > lockdep_match_key and that isn't defined unless CONFIG_DEBUG_LOCK_ALLOC
> > is set, I opted to make the caller require #ifdefing it still. If that's
> > too ugly, I could define it in both cases but then we'd have an exported
> > symbol that did nothing when the config option is disabled.
>
>
> > diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
> > index 87b6e04..ab956c8 100644
> > --- a/fs/hugetlbfs/inode.c
> > +++ b/fs/hugetlbfs/inode.c
> > @@ -491,6 +491,9 @@ static struct inode *hugetlbfs_get_inode(struct super_block *sb, uid_t uid,
> > inode->i_op = &page_symlink_inode_operations;
> > break;
> > }
> > +#ifdef CONFIG_DEBUG_LOCK_ALLOC
> > + lockdep_annotate_inode_mutex_key(inode);
> > +#endif
> > }
> > return inode;
> > }
> > diff --git a/fs/inode.c b/fs/inode.c
> > index 73920d5..ec1c612 100644
> > --- a/fs/inode.c
> > +++ b/fs/inode.c
> > @@ -848,16 +848,9 @@ struct inode *new_inode(struct super_block *sb)
> > }
> > EXPORT_SYMBOL(new_inode);
> >
> > -/**
> > - * unlock_new_inode - clear the I_NEW state and wake up any waiters
> > - * @inode: new inode to unlock
> > - *
> > - * Called when the inode is fully initialised to clear the new state of the
> > - * inode and wake up anyone waiting for the inode to finish initialisation.
> > - */
> > -void unlock_new_inode(struct inode *inode)
> > -{
> > #ifdef CONFIG_DEBUG_LOCK_ALLOC
> > +void lockdep_annotate_inode_mutex_key(struct inode *inode)
> > +{
> > if (S_ISDIR(inode->i_mode)) {
> > struct file_system_type *type = inode->i_sb->s_type;
> >
> > @@ -873,6 +866,21 @@ void unlock_new_inode(struct inode *inode)
> > &type->i_mutex_dir_key);
> > }
> > }
> > +}
> > +EXPORT_SYMBOL(lockdep_annotate_inode_mutex_key);
> > +#endif
> > +
> > +/**
> > + * unlock_new_inode - clear the I_NEW state and wake up any waiters
> > + * @inode: new inode to unlock
> > + *
> > + * Called when the inode is fully initialised to clear the new state of the
> > + * inode and wake up anyone waiting for the inode to finish initialisation.
> > + */
> > +void unlock_new_inode(struct inode *inode)
> > +{
>
> > + lockdep_annotate_inode_mutex_key(inode);
>
> > spin_lock(&inode->i_lock);
> > WARN_ON(!(inode->i_state & I_NEW));
> > diff --git a/include/linux/fs.h b/include/linux/fs.h
> > index 178cdb4..a29f9af 100644
> > --- a/include/linux/fs.h
> > +++ b/include/linux/fs.h
> > @@ -2318,6 +2318,9 @@ extern struct inode * iget5_locked(struct super_block *, unsigned long, int (*te
> > extern struct inode * iget_locked(struct super_block *, unsigned long);
> > extern int insert_inode_locked4(struct inode *, unsigned long, int (*test)(struct inode *, void *), void *);
> > extern int insert_inode_locked(struct inode *);
> > +#ifdef CONFIG_DEBUG_LOCK_ALLOC
> > +extern void lockdep_annotate_inode_mutex_key(struct inode *inode);
>
> #else
> static inline void lockdep_annotate_inode_mutex_key(struct inode *inode) { };
>
> > +#endif
> > extern void unlock_new_inode(struct inode *);
> > extern unsigned int get_next_ino(void);
>
>
> Will avoid all the ifdeffery at usage sites nor need the pointless
> export.
Yep, I thought about that after I sent this last night. I'll fix it and
resend.
josh
prev parent reply other threads:[~2011-08-25 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 1:37 [RFC] lockdep: Add helper function for dir vs file i_mutex annotation Josh Boyer
2011-08-25 5:19 ` Christoph Hellwig
2011-08-25 8:58 ` Peter Zijlstra
2011-08-25 11:25 ` Josh Boyer [this message]
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=20110825112533.GN2270@zod.bos.redhat.com \
--to=jwboyer@redhat.com \
--cc=davej@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox