On Wed, 2019-04-24 at 13:53 +0800, Firo wrote:
>
> On 4/20/19 6:31 AM, Saeed Mahameed wrote:
> > On Fri, 2019-04-19 at 21:07 +0800, Firo wrote:
> > > On 4/19/19 2:17 AM, Saeed Mahameed wrote:
> > > > On Thu, 2019-04-18 at 15:05 +0800, Firo wrote:
> > > > > On 4/2/19 12:25 AM, Saeed Mahameed wrote:
On 4/20/19 6:31 AM, Saeed Mahameed wrote:
> On Fri, 2019-04-19 at 21:07 +0800, Firo wrote:
>>
>> On 4/19/19 2:17 AM, Saeed Mahameed wrote:
>>> On Thu, 2019-04-18 at 15:05 +0800, Firo wrote:
On 4/2/19 12:25 AM, Saeed Mahameed wrote:
> On Mon, 2019-04-01 at 20:24 +0800, Firo Yang wrote:
>
On Fri, 2019-04-19 at 21:07 +0800, Firo wrote:
>
> On 4/19/19 2:17 AM, Saeed Mahameed wrote:
> > On Thu, 2019-04-18 at 15:05 +0800, Firo wrote:
> > > On 4/2/19 12:25 AM, Saeed Mahameed wrote:
> > > > On Mon, 2019-04-01 at 20:24 +0800, Firo Yang wrote:
> > > > > This crash is triggered by a user-af
On 4/19/19 2:17 AM, Saeed Mahameed wrote:
> On Thu, 2019-04-18 at 15:05 +0800, Firo wrote:
>>
>> On 4/2/19 12:25 AM, Saeed Mahameed wrote:
>>> On Mon, 2019-04-01 at 20:24 +0800, Firo Yang wrote:
This crash is triggered by a user-after-free since lake of
the synchronization of a race co
On Thu, 2019-04-18 at 15:05 +0800, Firo wrote:
>
> On 4/2/19 12:25 AM, Saeed Mahameed wrote:
> > On Mon, 2019-04-01 at 20:24 +0800, Firo Yang wrote:
> > > This crash is triggered by a user-after-free since lake of
> > > the synchronization of a race condition between
> > > be_update_queues() modi
On 4/2/19 12:25 AM, Saeed Mahameed wrote:
> On Mon, 2019-04-01 at 20:24 +0800, Firo Yang wrote:
>> This crash is triggered by a user-after-free since lake of
>> the synchronization of a race condition between
>> be_update_queues() modifying multi-purpose channels of
>> network device and be_tx_
On 4/2/19 12:25 AM, Saeed Mahameed wrote:
> On Mon, 2019-04-01 at 20:24 +0800, Firo Yang wrote:
>> This crash is triggered by a user-after-free since lake of
>> the synchronization of a race condition between
>> be_update_queues() modifying multi-purpose channels of
>> network device and be_tx
On Mon, 2019-04-01 at 20:24 +0800, Firo Yang wrote:
> This crash is triggered by a user-after-free since lake of
> the synchronization of a race condition between
> be_update_queues() modifying multi-purpose channels of
> network device and be_tx_timeout().
>
> BUG: unable to handle kernel NULL p
This crash is triggered by a user-after-free since lake of
the synchronization of a race condition between
be_update_queues() modifying multi-purpose channels of
network device and be_tx_timeout().
BUG: unable to handle kernel NULL pointer dereference at (null)
Call Trace:
be_tx_timeout+0xa5/0x36
