From: Cong Wang <xiyou.wangcong@gmail.com>
To: Tung Quang Nguyen <tung.q.nguyen@dektech.com.au>
Cc: "tipc-discussion@lists.sourceforge.net"
<tipc-discussion@lists.sourceforge.net>,
Xin Long <lucien.xin@gmail.com>,
David Miller <davem@davemloft.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [tipc-discussion] [net v3 1/1] tipc: fix memory leak caused by tipc_buf_append()
Date: Wed, 28 Oct 2020 12:29:01 -0700 [thread overview]
Message-ID: <CAM_iQpXquceLTrbVER1mQGBWk3WFjDTAawNBVSj1a2R6OTp-9w@mail.gmail.com> (raw)
In-Reply-To: <DB7PR05MB431592FDCD6EEB96C8DB0EE688170@DB7PR05MB4315.eurprd05.prod.outlook.com>
On Tue, Oct 27, 2020 at 10:23 PM Tung Quang Nguyen
<tung.q.nguyen@dektech.com.au> wrote:
>
> Hi Cong,
>
> No, I have never ignored any comment from reviewers. I sent v2 on Oct 26 after discussing with Xin Long, and v3 on Oct 27 after receiving comment from Jakub.
> I received your 3 emails nearly at the same time on Oct 28. It's weird. Your emails did not appear in this email archive either: https://sourceforge.net/p/tipc/mailman/tipc-discussion/
>
> Anyway, I answer your questions:
Oh, I just realized you meant shinfo->dataref, not skb->users...
Then it makes sense now.
Thanks.
next prev parent reply other threads:[~2020-10-29 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 3:24 [tipc-discussion] [net v3 1/1] tipc: fix memory leak caused by tipc_buf_append() Tung Nguyen
2020-10-27 20:50 ` Cong Wang
2020-10-28 5:23 ` Tung Quang Nguyen
2020-10-28 19:29 ` Cong Wang [this message]
2020-10-28 5:21 ` Xin Long
2020-10-28 19:31 ` Cong Wang
2020-10-29 16:55 ` Jakub Kicinski
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=CAM_iQpXquceLTrbVER1mQGBWk3WFjDTAawNBVSj1a2R6OTp-9w@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=davem@davemloft.net \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.q.nguyen@dektech.com.au \
/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).