From: Joe Perches <joe@perches.com>
To: John Fastabend <john.r.fastabend@intel.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Neil Horman <nhorman@tuxdriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: [flame^Wreview] net: netprio_cgroup: rework update socket logic
Date: Mon, 13 Aug 2012 02:08:31 -0700 [thread overview]
Message-ID: <1344848911.5849.10.camel@joe2Laptop> (raw)
In-Reply-To: <502896C5.7080303@intel.com>
On Sun, 2012-08-12 at 22:55 -0700, John Fastabend wrote:
> On 8/12/2012 6:53 PM, Al Viro wrote:
> > Ladies and gentlemen, who the devil had reviewed that little gem?
> >
> > commit 406a3c638ce8b17d9704052c07955490f732c2b8
> > Author: John Fastabend <john.r.fastabend@intel.com>
> > Date: Fri Jul 20 10:39:25 2012 +0000
[]
> OK clearly I screwed it up thanks for reviewing Al. How about this.
>
> fdt = files_fdtable(files);
> for (fd = 0; fd < fdt->max_fds; fd++) {
> struct socket *sock;
> int err = 0;
Don't need to initialize err if you're not using it.
> sock = sockfd_lookup(fd, &err);
> if (!sock) {
Of course you mean
if (sock)
> lock_sock(sock->sk);
> sock_update_netprioidx(sock->sk, p);
> release_sock(sock->sk);
> sockfd_put(sock);
> }
> }
next prev parent reply other threads:[~2012-08-13 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 1:53 [flame^Wreview] net: netprio_cgroup: rework update socket logic Al Viro
2012-08-13 2:30 ` Al Viro
2012-08-13 5:55 ` John Fastabend
2012-08-13 6:23 ` John Fastabend
2012-08-13 12:18 ` Al Viro
2012-08-13 16:58 ` John Fastabend
2012-08-13 17:01 ` Al Viro
2012-08-13 17:31 ` John Fastabend
2012-08-13 9:08 ` Joe Perches [this message]
2012-08-13 11:22 ` Neil Horman
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=1344848911.5849.10.camel@joe2Laptop \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=john.r.fastabend@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=viro@ZenIV.linux.org.uk \
/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).