From: Dan Carpenter <dan.carpenter@linaro.org>
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: Duoming Zhou <duoming@zju.edu.cn>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hams@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, jreuter@yaina.de
Subject: Re: [PATCH net v5 1/4] ax25: Use kernel universal linked list to implement ax25_dev_list
Date: Tue, 7 May 2024 12:52:03 +0300 [thread overview]
Message-ID: <5863f2fc-ab8e-4f6e-873e-2667bc0a2e4b@moroto.mountain> (raw)
In-Reply-To: <20240507092917.GA1049473@maili.marvell.com>
On Tue, May 07, 2024 at 02:59:17PM +0530, Ratheesh Kannoth wrote:
> On 2024-05-07 at 12:33:39, Duoming Zhou (duoming@zju.edu.cn) wrote:
> > The origin ax25_dev_list implements its own single linked list,
> > which is complicated and error-prone. For example, when deleting
> > the node of ax25_dev_list in ax25_dev_device_down(), we have to
> > operate on the head node and other nodes separately.
> >
> > This patch uses kernel universal linked list to replace original
> > ax25_dev_list, which make the operation of ax25_dev_list easier.
> > There are two points that need to notice:
> >
> > [1] We should add a check to judge whether the list is empty before
> > INIT_LIST_HEAD in ax25_dev_device_up(), otherwise it will empty the
> > list for each new ax25_dev added.
> >
> > [2] We should do "dev->ax25_ptr = ax25_dev;" and "dev->ax25_ptr = NULL;"
> > while holding the spinlock, otherwise the ax25_dev_device_up() and
> > ax25_dev_device_down() could race, we're not guaranteed to find a match
> > ax25_dev in ax25_dev_device_down().
> >
> > Suggested-by: Dan Carpenter <dan.carpenter@linaro.org>
> > Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
> > -ax25_dev *ax25_dev_list;
> > +static struct list_head ax25_dev_list;
> > DEFINE_SPINLOCK(ax25_dev_lock);
> >
> > ax25_dev *ax25_addr_ax25dev(ax25_address *addr)
> > @@ -34,7 +35,7 @@ ax25_dev *ax25_addr_ax25dev(ax25_address *addr)
> > ax25_dev *ax25_dev, *res = NULL;
> >
> > spin_lock_bh(&ax25_dev_lock);
> > - for (ax25_dev = ax25_dev_list; ax25_dev != NULL; ax25_dev = ax25_dev->next)
> > + list_for_each_entry(ax25_dev, &ax25_dev_list, list)
> > if (ax25cmp(addr, (const ax25_address *)ax25_dev->dev->dev_addr) == 0) {
> > res = ax25_dev;
> > ax25_dev_hold(ax25_dev);
> > @@ -52,6 +53,9 @@ void ax25_dev_device_up(struct net_device *dev)
> > {
> > ax25_dev *ax25_dev;
> >
> > + /* Initialized the list for the first entry */
> > + if (!ax25_dev_list.next)
> > + INIT_LIST_HEAD(&ax25_dev_list);
> if you define ax25_dev_list using 'static LIST_HEAD(ax25_dev_list)', you need this conditional check and
> initialization ?
>
Ah, yes. That's the proper way to do it.
regards,
dan carpenter
next prev parent reply other threads:[~2024-05-07 10:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 7:03 [PATCH net v5 0/4] ax25: Fix issues of ax25_dev and net_device Duoming Zhou
2024-05-07 7:03 ` [PATCH net v5 1/4] ax25: Use kernel universal linked list to implement ax25_dev_list Duoming Zhou
2024-05-07 8:48 ` Markus Elfring
2024-05-07 9:29 ` Ratheesh Kannoth
2024-05-07 9:52 ` Dan Carpenter [this message]
2024-05-07 19:43 ` Lars Kellogg-Stedman
2024-05-07 23:46 ` Lars Kellogg-Stedman
2024-05-07 7:03 ` [PATCH net v5 2/4] ax25: Fix reference count leak issues of ax25_dev Duoming Zhou
2024-05-07 9:12 ` Markus Elfring
2024-05-07 7:03 ` [PATCH net v5 3/4] ax25: Fix reference count leak issues of net_device Duoming Zhou
2024-05-07 9:25 ` Markus Elfring
2024-05-07 7:03 ` [PATCH net v5 4/4] ax25: Change kfree() in ax25_dev_free() to ax25_dev_put() Duoming Zhou
2024-05-07 9:42 ` Markus Elfring
2024-05-07 14:13 ` Ratheesh Kannoth
2024-05-07 10:00 ` [PATCH net v5 0/4] ax25: Fix issues of ax25_dev and net_device Markus Elfring
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=5863f2fc-ab8e-4f6e-873e-2667bc0a2e4b@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=jreuter@yaina.de \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.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
all inboxes | Powered by JetHome®