Avoid lockdep warnings.

uprobe_fork_uproc() runs with parent_uproc->rwsem locked.
However uprobe_mk_process() that gets called within uprobe_fork_uproc()
also locks child_uproc->rwsem after initializing it.

Lockdep report confuses this to acquiring a lock that already has been
acquired and suggests using sub-classes.

The alternatives we have are:
1. use classes level to distinguish different uproc structures.
2. unlock parent_uproc->rwsem before we call uprobe_fork_uproc().
3. dont try locking child_uproc->rwsem; since we are protected by
   uproc_mutex as well as parent_uproc->rwsem;

We use the last approach.

Signed-off-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
---

0 files changed, 0 insertions, 0 deletions