On 11/29/16 10:56 AM, Jeff Mahoney wrote:
> On 11/29/16 1:36 AM, Chandan Rajendra wrote:
>> When executing btrfs/126 test on kdave/for-next branch on a ppc64 guest, I
>> noticed the following call trace.
>>
>> [ 77.335887] [ cut here ]
>> [ 77.336115] WARNING: CPU: 0 PID
On 11/29/16 1:36 AM, Chandan Rajendra wrote:
> When executing btrfs/126 test on kdave/for-next branch on a ppc64 guest, I
> noticed the following call trace.
>
> [ 77.335887] [ cut here ]
> [ 77.336115] WARNING: CPU: 0 PID: 8325 at
> /root/repos/linux/fs/btrfs/qgroup.c
On Tuesday, November 29, 2016 04:41:41 PM Qu Wenruo wrote:
>
> At 11/29/2016 04:21 PM, Chandan Rajendra wrote:
> > On Tuesday, November 29, 2016 03:55:53 PM Qu Wenruo wrote:
> >> At 11/29/2016 02:36 PM, Chandan Rajendra wrote:
> >>> When executing btrfs/126 test on kdave/for-next branch on a ppc64
At 11/29/2016 04:21 PM, Chandan Rajendra wrote:
On Tuesday, November 29, 2016 03:55:53 PM Qu Wenruo wrote:
At 11/29/2016 02:36 PM, Chandan Rajendra wrote:
When executing btrfs/126 test on kdave/for-next branch on a ppc64 guest, I
noticed the following call trace.
[ 77.335887] [
On Tuesday, November 29, 2016 03:55:53 PM Qu Wenruo wrote:
> At 11/29/2016 02:36 PM, Chandan Rajendra wrote:
> > When executing btrfs/126 test on kdave/for-next branch on a ppc64 guest, I
> > noticed the following call trace.
> >
> > [ 77.335887] [ cut here ]
> > [ 77.33
At 11/29/2016 02:36 PM, Chandan Rajendra wrote:
When executing btrfs/126 test on kdave/for-next branch on a ppc64 guest, I
noticed the following call trace.
[ 77.335887] [ cut here ]
[ 77.336115] WARNING: CPU: 0 PID: 8325 at
/root/repos/linux/fs/btrfs/qgroup.c:2443 .
Thanks for the detailed reports and reproducer.
I'll investigate it soon.
Thanks,
Qu
At 11/29/2016 02:36 PM, Chandan Rajendra wrote:
When executing btrfs/126 test on kdave/for-next branch on a ppc64 guest, I
noticed the following call trace.
[ 77.335887] [ cut here ]