From: Eric Dumazet <eric.dumazet@gmail.com>
To: Gao feng <gaofeng@cn.fujitsu.com>
Cc: nhorman@tuxdriver.com, davem@davemloft.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
lizefan@huawei.com, tj@kernel.org,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH] net: cgroup: fix access the unallocated memory in netprio cgroup
Date: Tue, 10 Jul 2012 11:15:07 +0200 [thread overview]
Message-ID: <1341911707.3265.4603.camel@edumazet-glaptop> (raw)
In-Reply-To: <4FFBED84.1030905@cn.fujitsu.com>
On Tue, 2012-07-10 at 16:53 +0800, Gao feng wrote:
> > Hi Gao
> >
> > Is it still needed to call update_netdev_tables() from write_priomap() ?
> >
>
> Yes, I think it's needed,because read_priomap will show all of the net devices,
>
> But we may add the netdev after create a netprio cgroup, so the new added netdev's
> priomap will not be allocated. if we don't call update_netdev_tables in write_priomap,
> we may access this unallocated memory.
>
I realize my question was not clear.
If we write in write_priomap() a field of a single netdevice,
why should we allocate memory for all netdevices on the machine ?
So the question was : Do we really need to call
update_netdev_tables(alldevs), instead of extend_netdev_table(dev)
next prev parent reply other threads:[~2012-07-10 9:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 7:45 [PATCH] net: cgroup: fix out of bounds accesses Eric Dumazet
2012-07-09 8:15 ` Gao feng
2012-07-09 21:51 ` David Miller
2012-07-10 2:33 ` Gao feng
2012-07-10 2:37 ` David Miller
2012-07-09 11:01 ` Neil Horman
2012-07-09 11:50 ` Eric Dumazet
2012-07-09 12:13 ` Neil Horman
2012-07-09 12:40 ` Eric Dumazet
2012-07-09 12:56 ` Neil Horman
2012-07-10 2:31 ` [PATCH] net: cgroup: fix access the unallocated memory in netprio cgroup Gao feng
2012-07-10 4:14 ` Eric Dumazet
2012-07-10 8:53 ` Gao feng
2012-07-10 9:15 ` Eric Dumazet [this message]
2012-07-10 9:36 ` Gao feng
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=1341911707.3265.4603.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gaofeng@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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