Re: [PATCH 0/5] locks: move most locks_release_private calls outside of i_lock

From: Christoph Hellwig
Date: Tue Aug 12 2014 - 11:32:34 EST

Next message: Aneesh Kumar K.V: "Re: [PATCH] hugetlb_cgroup: use lockdep_assert_held rather than spin_is_locked"
Previous message: Ohad Ben-Cohen: "Re: [PATCH] rpmsg: compute number of buffers to allocate from vrings"
In reply to: Jeff Layton: "[PATCH 1/5] locks: don't call locks_release_private from locks_copy_lock"
Next in thread: Jeff Layton: "Re: [PATCH 0/5] locks: move most locks_release_private calls outside of i_lock"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Btw, I might be missing something here, but wouldn't it be better
to reference count the file_lock structure and grab a reference to
it where we currently call (__)locks_copy_lock?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Aneesh Kumar K.V: "Re: [PATCH] hugetlb_cgroup: use lockdep_assert_held rather than spin_is_locked"
Previous message: Ohad Ben-Cohen: "Re: [PATCH] rpmsg: compute number of buffers to allocate from vrings"
In reply to: Jeff Layton: "[PATCH 1/5] locks: don't call locks_release_private from locks_copy_lock"
Next in thread: Jeff Layton: "Re: [PATCH 0/5] locks: move most locks_release_private calls outside of i_lock"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]