Re: [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node

2017-06-05 Thread Stephen Rothwell
Hi David, On Mon, 5 Jun 2017 13:43:06 +0200 David Sterba wrote: > > Now fixed, sorry. Top commit 736202ae51c50a6063087011073e91b6a6ae92e9. I > didn't notice the patch got back to for-next through another branch. Ah ha. Thanks. -- Cheers, Stephen Rothwell

Re: [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node

2017-06-05 Thread David Sterba
On Mon, Jun 05, 2017 at 01:30:23PM +1000, Stephen Rothwell wrote: > Hi David, > > On Wed, 31 May 2017 16:58:48 +0200 David Sterba wrote: > > > > On Wed, May 31, 2017 at 02:29:20AM -0700, Omar Sandoval wrote: > > > diff --git a/fs/btrfs/free-space-tree.c b/fs/btrfs/free-space-tree.c > > > index fc

Re: [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node

2017-06-04 Thread Stephen Rothwell
Hi David, On Wed, 31 May 2017 16:58:48 +0200 David Sterba wrote: > > On Wed, May 31, 2017 at 02:29:20AM -0700, Omar Sandoval wrote: > > diff --git a/fs/btrfs/free-space-tree.c b/fs/btrfs/free-space-tree.c > > index fc0bd8406758..5abd3cd71144 100644 > > --- a/fs/btrfs/free-space-tree.c > > +++ b/f

Re: [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node

2017-05-31 Thread David Sterba
On Wed, May 31, 2017 at 02:29:20AM -0700, Omar Sandoval wrote: > diff --git a/fs/btrfs/free-space-tree.c b/fs/btrfs/free-space-tree.c > index fc0bd8406758..5abd3cd71144 100644 > --- a/fs/btrfs/free-space-tree.c > +++ b/fs/btrfs/free-space-tree.c > @@ -153,21 +153,18 @@ static inline u32 free_space_

Re: [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node

2017-05-31 Thread Michal Hocko
On Wed 31-05-17 02:29:20, Omar Sandoval wrote: > On Wed, May 31, 2017 at 11:19:05AM +0200, Michal Hocko wrote: > > On Wed 31-05-17 02:12:02, Omar Sandoval wrote: > > > On Wed, May 31, 2017 at 08:51:28AM +0200, Michal Hocko wrote: > > > > On Wed 31-05-17 14:30:33, kernel test robot wrote: > > > > >

Re: [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node

2017-05-31 Thread Omar Sandoval
On Wed, May 31, 2017 at 11:19:05AM +0200, Michal Hocko wrote: > On Wed 31-05-17 02:12:02, Omar Sandoval wrote: > > On Wed, May 31, 2017 at 08:51:28AM +0200, Michal Hocko wrote: > > > On Wed 31-05-17 14:30:33, kernel test robot wrote: > > > > > > > > FYI, we noticed the following commit: > > > > >

Re: [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node

2017-05-31 Thread Michal Hocko
On Wed 31-05-17 02:12:02, Omar Sandoval wrote: > On Wed, May 31, 2017 at 08:51:28AM +0200, Michal Hocko wrote: > > On Wed 31-05-17 14:30:33, kernel test robot wrote: > > > > > > FYI, we noticed the following commit: > > > > > > commit: beeeccca9bebcec386cc31c250cff8a06cf27034 ("btrfs: Use kvzallo

Re: [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node

2017-05-31 Thread Omar Sandoval
On Wed, May 31, 2017 at 08:51:28AM +0200, Michal Hocko wrote: > On Wed 31-05-17 14:30:33, kernel test robot wrote: > > > > FYI, we noticed the following commit: > > > > commit: beeeccca9bebcec386cc31c250cff8a06cf27034 ("btrfs: Use kvzalloc > > instead of kzalloc/vmalloc in alloc_bitmap") > > htt

Re: [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node

2017-05-30 Thread Michal Hocko
On Wed 31-05-17 14:30:33, kernel test robot wrote: > > FYI, we noticed the following commit: > > commit: beeeccca9bebcec386cc31c250cff8a06cf27034 ("btrfs: Use kvzalloc > instead of kzalloc/vmalloc in alloc_bitmap") > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master I have

[lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node

2017-05-30 Thread kernel test robot
FYI, we noticed the following commit: commit: beeeccca9bebcec386cc31c250cff8a06cf27034 ("btrfs: Use kvzalloc instead of kzalloc/vmalloc in alloc_bitmap") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -c