netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: subashab@codeaurora.org
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, stranche@codeaurora.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: rmnet: fix interface leak for rmnet module
Date: Thu, 02 Jul 2020 22:01:43 -0600	[thread overview]
Message-ID: <73674e9e0936e664bb1787d233fa90b6@codeaurora.org> (raw)
In-Reply-To: <20200702170737.10479-1-ap420073@gmail.com>

On 2020-07-02 11:07, Taehee Yoo wrote:
> There are two problems in rmnet module that they occur the leak of
> a lower interface.
> The symptom is the same, which is the leak of a lower interface.
> But there are two different real problems.
> This patchset is to fix these real problems.
> 
> 1. Do not allow to have different two modes.
> As a lower interface of rmnet, there are two modes that they are VND
> and BRIDGE.
> One interface can have only one mode.
> But in the current rmnet, there is no code to prevent to have
> two modes in one lower interface.
> So, interface leak occurs.
> 
> 2. Do not allow to add multiple bridge interfaces.
> rmnet can have only two bridge interface.
> If an additional bridge interface is tried to be attached,
> rmnet should deny it.
> But there is no code to do that.
> So, interface leak occurs.
> 
> Taehee Yoo (2):
>   net: rmnet: fix lower interface leak
>   net: rmnet: do not allow to add multiple bridge interfaces
> 
>  .../net/ethernet/qualcomm/rmnet/rmnet_config.c | 18 +++++++++++++-----
>  1 file changed, 13 insertions(+), 5 deletions(-)

Thanks Taehee. For the series-

Reviewed-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>

  reply	other threads:[~2020-07-03  4:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 17:07 [PATCH net 0/2] net: rmnet: fix interface leak for rmnet module Taehee Yoo
2020-07-03  4:01 ` subashab [this message]
2020-07-05  1:05 ` David Miller

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=73674e9e0936e664bb1787d233fa90b6@codeaurora.org \
    --to=subashab@codeaurora.org \
    --cc=ap420073@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stranche@codeaurora.org \
    /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).