Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1639243 > unrolled thread
| Started by | Lars Ellenberg <lars.ellenberg@linbit.com> |
|---|---|
| First post | 2017-05-11 10:40 +0200 |
| Last post | 2017-05-11 18:10 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.kernel
[PATCH] drbd: fix request leak introduced by locking/atomic, kref: Kill kref_sub() Lars Ellenberg <lars.ellenberg@linbit.com> - 2017-05-11 10:40 +0200
Re: [PATCH] drbd: fix request leak introduced by locking/atomic, kref: Kill kref_sub() Peter Zijlstra <peterz@infradead.org> - 2017-05-11 10:40 +0200
Re: [PATCH] drbd: fix request leak introduced by locking/atomic, kref: Kill kref_sub() Jens Axboe <axboe@kernel.dk> - 2017-05-11 18:10 +0200
| From | Lars Ellenberg <lars.ellenberg@linbit.com> |
|---|---|
| Date | 2017-05-11 10:40 +0200 |
| Subject | [PATCH] drbd: fix request leak introduced by locking/atomic, kref: Kill kref_sub() |
| Message-ID | <tFRND-40O-11@gated-at.bofh.it> |
Regression fix for 4.11, which totally broke DRBD
When killing kref_sub(), the unconditional additional kref_get()
was not properly paired with the necessary kref_put(), causing
a leak of struct drbd_requests (~ 224 Bytes) per submitted bio,
and breaking DRBD in general, as the destructor of those "drbd_requests"
does more than just the mempoll_free().
Fixes: bdfafc4ffdd2 ("locking/atomic, kref: Kill kref_sub()")
Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
---
drivers/block/drbd/drbd_req.c | 27 +++++++++++++++------------
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a/drivers/block/drbd/drbd_req.c b/drivers/block/drbd/drbd_req.c
index 652114a..1fc8a67 100644
--- a/drivers/block/drbd/drbd_req.c
+++ b/drivers/block/drbd/drbd_req.c
@@ -314,24 +314,32 @@ void drbd_req_complete(struct drbd_request *req, struct bio_and_error *m)
}
/* still holds resource->req_lock */
-static int drbd_req_put_completion_ref(struct drbd_request *req, struct bio_and_error *m, int put)
+static void drbd_req_put_completion_ref(struct drbd_request *req, struct bio_and_error *m, int put)
{
struct drbd_device *device = req->device;
D_ASSERT(device, m || (req->rq_state & RQ_POSTPONED));
+ if (!put)
+ return;
+
if (!atomic_sub_and_test(put, &req->completion_ref))
- return 0;
+ return;
drbd_req_complete(req, m);
+ /* local completion may still come in later,
+ * we need to keep the req object around. */
+ if (req->rq_state & RQ_LOCAL_ABORTED)
+ return;
+
if (req->rq_state & RQ_POSTPONED) {
/* don't destroy the req object just yet,
* but queue it for retry */
drbd_restart_request(req);
- return 0;
+ return;
}
- return 1;
+ kref_put(&req->kref, drbd_req_destroy);
}
static void set_if_null_req_next(struct drbd_peer_device *peer_device, struct drbd_request *req)
@@ -518,12 +526,8 @@ static void mod_rq_state(struct drbd_request *req, struct bio_and_error *m,
if (req->i.waiting)
wake_up(&device->misc_wait);
- if (c_put) {
- if (drbd_req_put_completion_ref(req, m, c_put))
- kref_put(&req->kref, drbd_req_destroy);
- } else {
- kref_put(&req->kref, drbd_req_destroy);
- }
+ drbd_req_put_completion_ref(req, m, c_put);
+ kref_put(&req->kref, drbd_req_destroy);
}
static void drbd_report_io_error(struct drbd_device *device, struct drbd_request *req)
@@ -1363,8 +1367,7 @@ static void drbd_send_and_submit(struct drbd_device *device, struct drbd_request
}
out:
- if (drbd_req_put_completion_ref(req, &m, 1))
- kref_put(&req->kref, drbd_req_destroy);
+ drbd_req_put_completion_ref(req, &m, 1);
spin_unlock_irq(&resource->req_lock);
/* Even though above is a kref_put(), this is safe.
--
2.7.4
[toc] | [next] | [standalone]
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Date | 2017-05-11 10:40 +0200 |
| Subject | Re: [PATCH] drbd: fix request leak introduced by locking/atomic, kref: Kill kref_sub() |
| Message-ID | <tFRNE-40O-19@gated-at.bofh.it> |
| In reply to | #1639243 |
On Thu, May 11, 2017 at 10:21:46AM +0200, Lars Ellenberg wrote:
> Regression fix for 4.11, which totally broke DRBD
>
> When killing kref_sub(), the unconditional additional kref_get()
> was not properly paired with the necessary kref_put(), causing
> a leak of struct drbd_requests (~ 224 Bytes) per submitted bio,
> and breaking DRBD in general, as the destructor of those "drbd_requests"
> does more than just the mempoll_free().
>
> Fixes: bdfafc4ffdd2 ("locking/atomic, kref: Kill kref_sub()")
> Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
Dang, sorry about that. Thanks for fixing it.
[toc] | [prev] | [next] | [standalone]
| From | Jens Axboe <axboe@kernel.dk> |
|---|---|
| Date | 2017-05-11 18:10 +0200 |
| Subject | Re: [PATCH] drbd: fix request leak introduced by locking/atomic, kref: Kill kref_sub() |
| Message-ID | <tFYP9-7g-43@gated-at.bofh.it> |
| In reply to | #1639243 |
On 05/11/2017 02:21 AM, Lars Ellenberg wrote: > Regression fix for 4.11, which totally broke DRBD > > When killing kref_sub(), the unconditional additional kref_get() > was not properly paired with the necessary kref_put(), causing > a leak of struct drbd_requests (~ 224 Bytes) per submitted bio, > and breaking DRBD in general, as the destructor of those "drbd_requests" > does more than just the mempoll_free(). Ugh... Applied for this series. I'll mark it stable for 4.11. -- Jens Axboe
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web