From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Jakob Koschel <jakobkoschel@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, "Bos, H.J." <h.j.bos@vu.nl>,
Brian Johannesmeyer <bjohannesmeyer@gmail.com>,
linux-block@vger.kernel.org,
Cristiano Giuffrida <c.giuffrida@vu.nl>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
Mike Rapoport <rppt@kernel.org>,
drbd-dev@lists.linbit.com,
Philipp Reisner <philipp.reisner@linbit.com>
Subject: Re: [Drbd-dev] [PATCH 2/2] drbd: remove check of list iterator against head past the loop body
Date: Fri, 1 Apr 2022 00:28:19 +0200 [thread overview]
Message-ID: <4dcedb78-355f-ed1a-9af1-27e9e63b5643@linbit.com> (raw)
In-Reply-To: <20220331220349.885126-2-jakobkoschel@gmail.com>
Am 01.04.22 um 00:03 schrieb Jakob Koschel:
> When list_for_each_entry() completes the iteration over the whole list
> without breaking the loop, the iterator value will be a bogus pointer
> computed based on the head element.
>
> While it is safe to use the pointer to determine if it was computed
> based on the head element, either with list_entry_is_head() or
> &pos->member == head, using the iterator variable after the loop should
> be avoided.
>
> In preparation to limit the scope of a list iterator to the list
> traversal loop, use a dedicated pointer to point to the found element [1].
>
> Link: https://lore.kernel.org/all/CAHk-=wgRr_D8CB-D9Kg-c=EHreAsk5SqXPwr9Y7k9sA6cWXJ6w@mail.gmail.com/ [1]
> Signed-off-by: Jakob Koschel <jakobkoschel@gmail.com>
> ---
> drivers/block/drbd/drbd_req.c | 42 ++++++++++++++++++++++-------------
> 1 file changed, 27 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/block/drbd/drbd_req.c b/drivers/block/drbd/drbd_req.c
> index c04394518b07..b2571dc77fe6 100644
> --- a/drivers/block/drbd/drbd_req.c
> +++ b/drivers/block/drbd/drbd_req.c
> @@ -332,17 +332,21 @@ static void set_if_null_req_next(struct drbd_peer_device *peer_device, struct dr
> static void advance_conn_req_next(struct drbd_peer_device *peer_device, struct drbd_request *req)
> {
> struct drbd_connection *connection = peer_device ? peer_device->connection : NULL;
> + struct drbd_request *iter = req;
> if (!connection)
> return;
> if (connection->req_next != req)
> return;
> - list_for_each_entry_continue(req, &connection->transfer_log, tl_requests) {
> - const unsigned s = req->rq_state;
> - if (s & RQ_NET_QUEUED)
> +
> + req = NULL;
> + list_for_each_entry_continue(iter, &connection->transfer_log, tl_requests) {
> + const unsigned int s = iter->rq_state;
> +
> + if (s & RQ_NET_QUEUED) {
> + req = iter;
> break;
> + }
> }
> - if (&req->tl_requests == &connection->transfer_log)
> - req = NULL;
> connection->req_next = req;
> }
>
> @@ -358,17 +362,21 @@ static void set_if_null_req_ack_pending(struct drbd_peer_device *peer_device, st
> static void advance_conn_req_ack_pending(struct drbd_peer_device *peer_device, struct drbd_request *req)
> {
> struct drbd_connection *connection = peer_device ? peer_device->connection : NULL;
> + struct drbd_request *iter = req;
> if (!connection)
> return;
> if (connection->req_ack_pending != req)
> return;
> - list_for_each_entry_continue(req, &connection->transfer_log, tl_requests) {
> - const unsigned s = req->rq_state;
> - if ((s & RQ_NET_SENT) && (s & RQ_NET_PENDING))
> +
> + req = NULL;
> + list_for_each_entry_continue(iter, &connection->transfer_log, tl_requests) {
> + const unsigned int s = iter->rq_state;
> +
> + if ((s & RQ_NET_SENT) && (s & RQ_NET_PENDING)) {
> + req = iter;
> break;
> + }
> }
> - if (&req->tl_requests == &connection->transfer_log)
> - req = NULL;
> connection->req_ack_pending = req;
> }
>
> @@ -384,17 +392,21 @@ static void set_if_null_req_not_net_done(struct drbd_peer_device *peer_device, s
> static void advance_conn_req_not_net_done(struct drbd_peer_device *peer_device, struct drbd_request *req)
> {
> struct drbd_connection *connection = peer_device ? peer_device->connection : NULL;
> + struct drbd_request *iter = req;
> if (!connection)
> return;
> if (connection->req_not_net_done != req)
> return;
> - list_for_each_entry_continue(req, &connection->transfer_log, tl_requests) {
> - const unsigned s = req->rq_state;
> - if ((s & RQ_NET_SENT) && !(s & RQ_NET_DONE))
> +
> + req = NULL;
> + list_for_each_entry_continue(iter, &connection->transfer_log, tl_requests) {
> + const unsigned int s = iter->rq_state;
> +
> + if ((s & RQ_NET_SENT) && !(s & RQ_NET_DONE)) {
> + req = iter;
> break;
> + }
> }
> - if (&req->tl_requests == &connection->transfer_log)
> - req = NULL;
> connection->req_not_net_done = req;
> }
>
Hi Jakob,
Both of these look good to me, thanks.
Reviewed-by: Christoph Böhmwalder <christoph.boehmwalder@linbit.com>
Regards, Christoph
next prev parent reply other threads:[~2022-03-31 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 22:03 [PATCH 1/2] drbd: remove usage of list iterator variable after loop for list_for_each_entry_safe_from() Jakob Koschel
2022-03-31 22:03 ` [PATCH 2/2] drbd: remove check of list iterator against head past the loop body Jakob Koschel
2022-03-31 22:28 ` Christoph Böhmwalder [this message]
2022-03-31 23:09 ` [Drbd-dev] " Jens Axboe
2022-04-01 23:56 ` [PATCH 1/2] drbd: remove usage of list iterator variable after loop for list_for_each_entry_safe_from() Jens Axboe
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=4dcedb78-355f-ed1a-9af1-27e9e63b5643@linbit.com \
--to=christoph.boehmwalder@linbit.com \
--cc=axboe@kernel.dk \
--cc=bjohannesmeyer@gmail.com \
--cc=c.giuffrida@vu.nl \
--cc=drbd-dev@lists.linbit.com \
--cc=h.j.bos@vu.nl \
--cc=jakobkoschel@gmail.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@linbit.com \
--cc=rppt@kernel.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
all inboxes | Powered by JetHome®