linux-hams.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duoming Zhou <duoming@zju.edu.cn>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-hams@vger.kernel.org,
	pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
	davem@davemloft.net, jreuter@yaina.de, horms@kernel.org,
	Markus.Elfring@web.de, dan.carpenter@linaro.org, lars@oddbit.com,
	Duoming Zhou <duoming@zju.edu.cn>
Subject: [PATCH net v2 0/2] ax25: fix reference counting issue of ax25_dev
Date: Fri,  3 May 2024 07:36:14 +0800	[thread overview]
Message-ID: <cover.1714690906.git.duoming@zju.edu.cn> (raw)

The first patch changes kfree in ax25_dev_free to ax25_dev_put,
because the ax25_dev is managed by reference counting.

The second patch fixes potential reference counting leak issue
in ax25_addr_ax25dev.

You can see the former discussion in the following link:
https://lore.kernel.org/netdev/20240501060218.32898-1-duoming@zju.edu.cn/

Duoming Zhou (2):
  ax25: change kfree in ax25_dev_free to ax25_dev_free
  ax25: fix potential reference counting leak in ax25_addr_ax25dev

 net/ax25/ax25_dev.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

-- 
2.17.1


             reply	other threads:[~2024-05-02 23:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 23:36 Duoming Zhou [this message]
2024-05-02 23:36 ` [PATCH net v2 1/2] ax25: change kfree in ax25_dev_free to ax25_dev_free Duoming Zhou
2024-05-03  5:36   ` Markus Elfring
2024-05-03 11:33     ` Dan Carpenter
2024-05-02 23:36 ` [PATCH net v2 2/2] ax25: fix potential reference counting leak in ax25_addr_ax25dev Duoming Zhou
2024-05-03  7:30   ` Markus Elfring
2024-05-03 11:38     ` Dan Carpenter
2024-05-03 13:39       ` [v2 " Markus Elfring
2024-05-03  5:10 ` [PATCH net v2 0/2] ax25: fix reference counting issue of ax25_dev Dan Carpenter

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=cover.1714690906.git.duoming@zju.edu.cn \
    --to=duoming@zju.edu.cn \
    --cc=Markus.Elfring@web.de \
    --cc=dan.carpenter@linaro.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jreuter@yaina.de \
    --cc=kuba@kernel.org \
    --cc=lars@oddbit.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).