public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
	linux-sctp@vger.kernel.org, davem <davem@davemloft.net>,
	Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [PATCH net 1/3] sctp: sctp_sock_migrate() returns error if sctp_bind_addr_dup() fails
Date: Fri, 8 Mar 2019 13:59:09 -0300	[thread overview]
Message-ID: <20190308165909.GC13515@localhost.localdomain> (raw)
In-Reply-To: <CADvbK_cca0Xmxa2E=4JzyvVqaS8T-fbn5tt4h43dWDE5WTCZ2g@mail.gmail.com>

On Fri, Mar 08, 2019 at 11:48:10AM +0800, Xin Long wrote:
> On Fri, Mar 8, 2019 at 2:25 AM Marcelo Ricardo Leitner
> <marcelo.leitner@gmail.com> wrote:
> >
> > On Sun, Mar 03, 2019 at 05:54:53PM +0800, Xin Long wrote:
> > > It should fail to create the new sk if sctp_bind_addr_dup() fails
> > > when accepting or peeloff an association.
> > >
> > > Signed-off-by: Xin Long <lucien.xin@gmail.com>
> > > ---
> > >  net/sctp/socket.c | 34 ++++++++++++++++++++++++----------
> > >  1 file changed, 24 insertions(+), 10 deletions(-)
> > >
> > > diff --git a/net/sctp/socket.c b/net/sctp/socket.c
> > > index a2771b3..22adb8d 100644
> > > --- a/net/sctp/socket.c
> > > +++ b/net/sctp/socket.c
> > > @@ -102,9 +102,9 @@ static int sctp_send_asconf(struct sctp_association *asoc,
> > >                           struct sctp_chunk *chunk);
> > >  static int sctp_do_bind(struct sock *, union sctp_addr *, int);
> > >  static int sctp_autobind(struct sock *sk);
> > > -static void sctp_sock_migrate(struct sock *oldsk, struct sock *newsk,
> > > -                           struct sctp_association *assoc,
> > > -                           enum sctp_socket_type type);
> > > +static int sctp_sock_migrate(struct sock *oldsk, struct sock *newsk,
> > > +                          struct sctp_association *assoc,
> > > +                          enum sctp_socket_type type);
> > >
> > >  static unsigned long sctp_memory_pressure;
> > >  static atomic_long_t sctp_memory_allocated;
> > > @@ -4655,7 +4655,11 @@ static struct sock *sctp_accept(struct sock *sk, int flags, int *err, bool kern)
> > >       /* Populate the fields of the newsk from the oldsk and migrate the
> > >        * asoc to the newsk.
> > >        */
> > > -     sctp_sock_migrate(sk, newsk, asoc, SCTP_SOCKET_TCP);
> > > +     error = sctp_sock_migrate(sk, newsk, asoc, SCTP_SOCKET_TCP);
> > > +     if (error) {
> > > +             sk_common_release(newsk);
> > > +             newsk = NULL;
> > > +     }
> > >
> > >  out:
> > >       release_sock(sk);
> > > @@ -5401,7 +5405,12 @@ int sctp_do_peeloff(struct sock *sk, sctp_assoc_t id, struct socket **sockp)
> > >       /* Populate the fields of the newsk from the oldsk and migrate the
> > >        * asoc to the newsk.
> > >        */
> > > -     sctp_sock_migrate(sk, sock->sk, asoc, SCTP_SOCKET_UDP_HIGH_BANDWIDTH);
> > > +     err = sctp_sock_migrate(sk, sock->sk, asoc,
> > > +                             SCTP_SOCKET_UDP_HIGH_BANDWIDTH);
> > > +     if (err) {
> > > +             sock_release(sock);
> >
> > I'm having a hard time understanding why it needs sock_release() here
> > and sk_common_release() in the above chunk. AFAICT by here (after
> > sctp_sock_migrate call) the sockets are pretty much the same. Mind
> > elaborating please?
> In sctp_do_peeloff(),'sock' is 'struct socket' created by sock_create(),
> which should be freed by sock_release(struct socket *sock), otherwise
> no place takes care of its freeing.
> (sock_create() also create sock->sk)
> 
> In sctp_accept(), 'newsk' is 'struct sock' created by sk_alloc(), and
> it should be freed by sk_common_release(). Note by then sock->sk is not
> yet set to 'newsk', so when it return errs, outside can't free newsk
> when freeing sock.
> (sys_accept() calls sock_alloc() directly that doesn't set sock->sk)

Thanks.

  Marcelo

  reply	other threads:[~2019-03-08 16:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03  9:54 [PATCH net 0/3] sctp: process the error returned from sctp_sock_migrate() Xin Long
2019-03-03  9:54 ` [PATCH net 1/3] sctp: sctp_sock_migrate() returns error if sctp_bind_addr_dup() fails Xin Long
2019-03-06 18:21   ` Neil Horman
2019-03-07 10:06     ` Xin Long
2019-03-07 11:59       ` Neil Horman
2019-03-07 18:25   ` Marcelo Ricardo Leitner
2019-03-08  3:48     ` Xin Long
2019-03-08 16:59       ` Marcelo Ricardo Leitner [this message]
2019-03-03  9:54 ` [PATCH net 2/3] sctp: move up sctp_auth_init_hmacs() in sctp_endpoint_init() Xin Long
2019-03-06 18:24   ` Neil Horman
2019-03-03  9:54 ` [PATCH net 3/3] sctp: call sctp_auth_init_hmacs() in sctp_sock_migrate() Xin Long
2019-03-06 18:26   ` Neil Horman
2019-03-04 19:04 ` [PATCH net 0/3] sctp: process the error returned from sctp_sock_migrate() David Miller
2019-03-07 14:59   ` Marcelo Ricardo Leitner
2019-03-07 12:11 ` Neil Horman
2019-03-08 17:00 ` Marcelo Ricardo Leitner
2019-03-08 19:43   ` 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=20190308165909.GC13515@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.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