linux-sctp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: marcelo.leitner@gmail.com
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
	vyasevich@gmail.com, nhorman@tuxdriver.com
Subject: Re: [PATCH net-next] sctp: avoid list_del_init if it's freeing the memory right away
Date: Tue, 07 Feb 2017 19:21:21 +0000	[thread overview]
Message-ID: <20170207.142121.1027174926882132252.davem@davemloft.net> (raw)
In-Reply-To: <e1b3b9b24f39ee82a3131a39a0413231ba54bc7c.1486494022.git.marcelo.leitner@gmail.com>

From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Date: Tue,  7 Feb 2017 17:03:21 -0200

> There is no reason to use list_del_init() in these places as we are
> going to free/destroy the memory in a few lines below.
> 
> Signed-off-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
> ---
>  net/sctp/associola.c     | 14 ++++----------
>  net/sctp/auth.c          |  8 ++------
>  net/sctp/chunk.c         |  4 ++--
>  net/sctp/outqueue.c      | 14 +++++++-------
>  net/sctp/sm_make_chunk.c |  3 +--
>  5 files changed, 16 insertions(+), 27 deletions(-)
> 
> diff --git a/net/sctp/associola.c b/net/sctp/associola.c
> index e50dc6d7543fd6acfa7442f3a9ee575203c7718d..7eb9dacfa53a438b20a34319cf01c6c9a591f0c3 100644
> --- a/net/sctp/associola.c
> +++ b/net/sctp/associola.c
> @@ -1638,25 +1638,19 @@ int sctp_assoc_set_id(struct sctp_association *asoc, gfp_t gfp)
>  static void sctp_assoc_free_asconf_queue(struct sctp_association *asoc)
>  {
>  	struct sctp_chunk *asconf;
> -	struct sctp_chunk *tmp;
>  
> -	list_for_each_entry_safe(asconf, tmp, &asoc->addip_chunk_list, list) {
> -		list_del_init(&asconf->list);
> +	list_for_each_entry(asconf, &asoc->addip_chunk_list, list)
>  		sctp_chunk_free(asconf);
> -	}
>  }

This leave freed memory on the asoc->addip_chunk_list, in fact why aren't you seeing
the BUG_ON() in sctp_chunk_destroy() get triggered?  If you elide the list_del() here
then the "list_empty(&chunk->list)" check there will not be true.

I don't think this transformation here is legal at all.

  reply	other threads:[~2017-02-07 19:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 19:03 [PATCH net-next] sctp: avoid list_del_init if it's freeing the memory right away Marcelo Ricardo Leitner
2017-02-07 19:21 ` David Miller [this message]
2017-02-07 19:45   ` Marcelo Ricardo Leitner
2017-02-07 20:22     ` David Miller
2017-02-08 19:57     ` Marcelo Ricardo Leitner

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=20170207.142121.1027174926882132252.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-sctp@vger.kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=vyasevich@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).