All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hangyu Hua <hbh25y@gmail.com>
To: Yasushi SHOJI <yashi@spacecubics.com>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
	stefan.maetje@esd.eu, Pavel Skripkin <paskripkin@gmail.com>,
	remigiusz.kollataj@mobica.com,
	linux-can <linux-can@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] can: mcba_usb: fix possible double dev_kfree_skb in mcba_usb_start_xmit
Date: Wed, 23 Mar 2022 10:12:15 +0800	[thread overview]
Message-ID: <2f7ed3fa-9fd0-4109-8cdd-815ff3cfb35e@gmail.com> (raw)
In-Reply-To: <CAGLTpnK=4Gd8S488osvrbttkMvtsPy8eCGspV4-=z2N3UGZ5rw@mail.gmail.com>

Hi yashi,

You are right. There are a series of the same problems about 
can_put_echo_skb.

This issue was discovered while I was discussing a incorrect patch with 
Marc. You can check this in

https://lore.kernel.org/all/20220225060019.21220-1-hbh25y@gmail.com/

So i submitted a new patch. This was the first place where the problem 
occurs. You can check this in

[1] https://lore.kernel.org/all/20220228083639.38183-1-hbh25y@gmail.com/

After a week, I realized it could be a series of problems. So
i submitted the following patches

[2] 
https://lore.kernel.org/all/0d2f9980-fb1d-4068-7868-effc77892a97@gmail.com/
[3] 
https://lore.kernel.org/all/de416319-c027-837d-4b8c-b8c3c37ed88e@gmail.com/
[4] https://lore.kernel.org/all/20220317081305.739554-1-mkl@pengutronix.de/

I think this is all affected. None of the four have been merged 
upstream. Do i need to remake all these four patches?

Thanks,
Hangyu






On 2022/3/23 07:08, Yasushi SHOJI wrote:
> Hi Hangyu,
> 
> On Fri, Mar 11, 2022 at 5:02 PM Hangyu Hua <hbh25y@gmail.com> wrote:
>>
>> There is no need to call dev_kfree_skb when usb_submit_urb fails beacause
>> can_put_echo_skb deletes original skb and can_free_echo_skb deletes the cloned
>> skb.
> 
> So, it's more like, "we don't need to call dev_kfree_skb() after
> can_put_echo_skb()
> because can_put_echo_skb() consumes the given skb.".  It seems it doesn't depend
> on the condition of usb_submit_urb().  Plus, we don't see the "cloned
> skb" at the
> call site.
> 
> Would you mind adding a comment on can_put_echo_skb(), in a separate patch,
> saying the fact that it consumes the skb?
> 
> ems_usb.c, gs_usb.c and possibly some others seem to call
> dev_kfree_skb() as well.
> Are they affected?
> 
> Best,

      reply	other threads:[~2022-03-23  2:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  8:02 [PATCH] can: mcba_usb: fix possible double dev_kfree_skb in mcba_usb_start_xmit Hangyu Hua
2022-03-21  1:47 ` Hangyu Hua
2022-03-22 23:08 ` Yasushi SHOJI
2022-03-23  2:12   ` Hangyu Hua [this message]

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=2f7ed3fa-9fd0-4109-8cdd-815ff3cfb35e@gmail.com \
    --to=hbh25y@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=paskripkin@gmail.com \
    --cc=remigiusz.kollataj@mobica.com \
    --cc=stefan.maetje@esd.eu \
    --cc=wg@grandegger.com \
    --cc=yashi@spacecubics.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.