;makita.toshi...@lab.ntt.co.jp; step...@networkplumber.org;
> >ebied...@xmission.com; f.faine...@gmail.com; linux-kernel@vger.kernel.org;
> >Wuyunfei; Qianhuibin (Huibin QIAN, Euler)
> >Subject: Re: [PATCH net/next] bridge:Add rcu read lock when delete br port
> >
> >O
e...@gmail.com; linux-kernel@vger.kernel.org;
>Wuyunfei; Qianhuibin (Huibin QIAN, Euler)
>Subject: Re: [PATCH net/next] bridge:Add rcu read lock when delete br port
>
>On Mon, Aug 04, 2014 at 11:37:56AM +0800, lichu...@huawei.com wrote:
>> From: Chunhe Li
>>
>> In the
On Mon, 4 Aug 2014 11:37:56 +0800
wrote:
> From: Chunhe Li
>
> In the br_hanle_frame function has a bug, when the bridge receive packets
> which go througth the br_handle_frame, get the net_bridge_port pointer "p",
> but don't check NULL pointer to use it. If somebody delete the bridge port
> a
On Mon, 4 Aug 2014 11:37:56 +0800
wrote:
> From: Chunhe Li
>
> In the br_hanle_frame function has a bug, when the bridge receive packets
> which go througth the br_handle_frame, get the net_bridge_port pointer "p",
> but don't check NULL pointer to use it. If somebody delete the bridge port
> a
On Mon, Aug 04, 2014 at 11:37:56AM +0800, lichu...@huawei.com wrote:
> From: Chunhe Li
>
> In the br_hanle_frame function has a bug, when the bridge receive packets
> which go througth the br_handle_frame, get the net_bridge_port pointer "p",
> but don't check NULL pointer to use it. If somebody
5 matches
Mail list logo