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 RESEND net v4 0/4] ax25: Fix issues of ax25_dev and net_device
Date: Tue, 7 May 2024 14:21:08 +0800 [thread overview]
Message-ID: <cover.1715062582.git.duoming@zju.edu.cn> (raw)
The first patch uses kernel universal linked list to implement
ax25_dev_list, which makes the operation of the list easier.
The second and third patch fix reference count leak issues of
the object "ax25_dev" and "net_device". The last patch uses
ax25_dev_put() to replace kfree() in ax25_dev_free().
You can see the former discussion in the following link:
https://lore.kernel.org/netdev/20240501060218.32898-1-duoming@zju.edu.cn/
Duoming Zhou (4):
ax25: Use kernel universal linked list to implement ax25_dev_list
ax25: Fix reference count leak issues of ax25_dev
ax25: Fix reference count leak issues of net_device
ax25: Change kfree() in ax25_dev_free() to ax25_dev_put()
include/net/ax25.h | 4 ++--
net/ax25/ax25_dev.c | 51 ++++++++++++++++-----------------------------
2 files changed, 20 insertions(+), 35 deletions(-)
--
2.17.1
next reply other threads:[~2024-05-07 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 6:21 Duoming Zhou [this message]
2024-05-07 6:21 ` [PATCH RESEND net v4 1/4] ax25: Use kernel universal linked list to implement ax25_dev_list Duoming Zhou
2024-05-07 7:52 ` Markus Elfring
2024-05-07 6:21 ` [PATCH RESEND net v4 2/4] ax25: Fix reference count leak issues of ax25_dev Duoming Zhou
2024-05-07 6:21 ` [PATCH RESEND net v4 3/4] ax25: Fix reference count leak issues of net_device Duoming Zhou
2024-05-07 7:30 ` [PATCH RESEND net v4 0/4] ax25: Fix issues of ax25_dev and net_device Markus Elfring
2024-05-07 7:48 ` duoming
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.1715062582.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).