public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Cong Wang <cwang@twopensource.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	cgroups@vger.kernel.org, netdev <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	tj@kernel.org, ssorce@redhat.com, jkaluza@redhat.com,
	lpoetter@redhat.com, kay@redhat.com
Subject: Re: [PATCH 2/2] net: Implement SO_PEERCGROUP
Date: Thu, 13 Mar 2014 09:48:40 -0400	[thread overview]
Message-ID: <20140313134840.GA18914@redhat.com> (raw)
In-Reply-To: <CAHA+R7OrNoa7_J-rOskxgdvkM5gAnQyoFBeCXSziY7XMd-yLNA@mail.gmail.com>

On Wed, Mar 12, 2014 at 01:58:57PM -0700, Cong Wang wrote:
> On Wed, Mar 12, 2014 at 1:46 PM, Vivek Goyal <vgoyal@redhat.com> wrote:
> > @@ -1098,6 +1135,16 @@ static int unix_stream_connect(struct socket *sock, struct sockaddr *uaddr,
> >         if (newsk == NULL)
> >                 goto out;
> >
> > +       err = init_peercgroup(newsk);
> > +       if (err)
> > +               goto out;
> > +
> > +       err = alloc_cgroup_path(sk);
> > +       if (err)
> > +               goto out;
> > +
> > +       err = -ENOMEM;
> > +
> 
> Don't we need to free the cgroup_path on error path
> in this function?

Previous allocated cgroup_path is now in newsk->cgroup_path and I was
relying on __sk_free() freeing that memory if error happens.

unix_release_sock(sk)
  sock_put()
    sk_free()
      __sk_free()
        kfree(sk->cgroup_path)

Do you see a problem with that?

Thanks
Vivek

  reply	other threads:[~2014-03-13 13:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 20:46 [PATCH 0/2][V2] net: Implement SO_PEERCGROUP to get cgroup of peer Vivek Goyal
2014-03-12 20:46 ` [PATCH 1/2] cgroup: Provide empty definition of task_cgroup_path() Vivek Goyal
2014-03-12 20:46 ` [PATCH 2/2] net: Implement SO_PEERCGROUP Vivek Goyal
2014-03-12 20:58   ` Cong Wang
2014-03-13 13:48     ` Vivek Goyal [this message]
2014-03-12 21:00   ` Andy Lutomirski
2014-03-12 21:12     ` Andy Lutomirski
2014-03-12 21:16       ` Simo Sorce
2014-03-12 21:19         ` Andy Lutomirski
2014-03-13  1:17           ` Simo Sorce
2014-03-13  1:21             ` Andy Lutomirski
2014-03-13  1:43               ` Simo Sorce
2014-03-13  2:12                 ` Andy Lutomirski
2014-03-13 14:27                   ` Vivek Goyal
2014-03-14 23:54                     ` Eric W. Biederman
2014-03-13 17:51                   ` Simo Sorce
2014-03-13 17:55                     ` Andy Lutomirski
2014-03-13 17:57                       ` Simo Sorce
2014-03-13 18:03                         ` Andy Lutomirski
2014-03-13 17:58                       ` Simo Sorce
2014-03-13 18:01                         ` Andy Lutomirski
2014-03-13 18:05                         ` Tim Hockin
2014-03-13 19:53                       ` Vivek Goyal
2014-03-13 19:58                         ` Andy Lutomirski
2014-03-13 20:06                           ` Vivek Goyal
2014-03-13 20:17                             ` Vivek Goyal
2014-03-13 20:19                               ` Vivek Goyal
2014-03-13 21:21                             ` Andy Lutomirski
2014-03-14 23:49                             ` Eric W. Biederman
2014-03-13 18:02                     ` Vivek Goyal
2014-03-13 14:14       ` Vivek Goyal
2014-03-13 14:55         ` Simo Sorce
2014-03-13 15:00           ` Vivek Goyal
2014-03-13 16:33             ` Simo Sorce
2014-03-13 17:25               ` Andy Lutomirski
2014-03-13 17:55                 ` Simo Sorce
2014-03-13 17:56                 ` Tim Hockin
2014-03-12 20:56 ` [PATCH 0/2][V2] net: Implement SO_PEERCGROUP to get cgroup of peer Andy Lutomirski
2014-03-12 20:59   ` Simo Sorce
2014-03-12 21:09     ` Andy Lutomirski
  -- strict thread matches above, loose matches on Subject: below --
2014-03-12 18:45 [PATCH 0/2] " Vivek Goyal
2014-03-12 18:45 ` [PATCH 2/2] net: Implement SO_PEERCGROUP Vivek Goyal

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=20140313134840.GA18914@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=cgroups@vger.kernel.org \
    --cc=cwang@twopensource.com \
    --cc=davem@davemloft.net \
    --cc=jkaluza@redhat.com \
    --cc=kay@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpoetter@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=ssorce@redhat.com \
    --cc=tj@kernel.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