Re: Re: linux-next memleak after IO on dax mountpoint

On 06/02/2016 08:22 AM, David Drysdale wrote: FWIW, I'm also seeing kmemleak report a leak with v4.7-rc1, in a different scenario (just normal desktop use). Not done much digging so far, but this commit (9082e87bf) looks like it might be relevant -- lots of the following: unreferenced object

Re: Re: linux-next memleak after IO on dax mountpoint

On 06/02/2016 08:22 AM, David Drysdale wrote: FWIW, I'm also seeing kmemleak report a leak with v4.7-rc1, in a different scenario (just normal desktop use). Not done much digging so far, but this commit (9082e87bf) looks like it might be relevant -- lots of the following: unreferenced object

Re: linux-next memleak after IO on dax mountpoint

On Sat, May 28, 2016 at 5:05 AM, Xiong Zhou wrote: > On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: > ... >> Still working on to id which commit in this merge causes this issuer, > > Narrowed down to: > > 37e5823 block: add offset in blk_add_request_payload() >

Re: linux-next memleak after IO on dax mountpoint

On Sat, May 28, 2016 at 5:05 AM, Xiong Zhou wrote: > On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: > ... >> Still working on to id which commit in this merge causes this issuer, > > Narrowed down to: > > 37e5823 block: add offset in blk_add_request_payload() > e048948 blk-mq: Export

Re: linux-next memleak after IO on dax mountpoint

Hi, Jeff On Wed, Jun 01, 2016 at 10:37:26AM -0400, Jeff Moyer wrote: > Xiong Zhou writes: > > > On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: > > ... > >> Still working on to id which commit in this merge causes this issuer, > > > > Narrowed down to: > > Hi

Re: linux-next memleak after IO on dax mountpoint

Hi, Jeff On Wed, Jun 01, 2016 at 10:37:26AM -0400, Jeff Moyer wrote: > Xiong Zhou writes: > > > On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: > > ... > >> Still working on to id which commit in this merge causes this issuer, > > > > Narrowed down to: > > Hi Xiong, > > I don't

Re: linux-next memleak after IO on dax mountpoint

Xiong Zhou writes: > On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: > ... >> Still working on to id which commit in this merge causes this issuer, > > Narrowed down to: Hi Xiong, I don't see how any of those could be at all relevant to pmem. Can you post the

Re: linux-next memleak after IO on dax mountpoint

Xiong Zhou writes: > On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: > ... >> Still working on to id which commit in this merge causes this issuer, > > Narrowed down to: Hi Xiong, I don't see how any of those could be at all relevant to pmem. Can you post the output from 'cat

Re: linux-next memleak after IO on dax mountpoint

On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: ... > Still working on to id which commit in this merge causes this issuer, Narrowed down to: 37e5823 block: add offset in blk_add_request_payload() e048948 blk-mq: Export tagset iter function 58b4560 nvme: add helper nvme_map_len()

Re: linux-next memleak after IO on dax mountpoint

On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: ... > Still working on to id which commit in this merge causes this issuer, Narrowed down to: 37e5823 block: add offset in blk_add_request_payload() e048948 blk-mq: Export tagset iter function 58b4560 nvme: add helper nvme_map_len()

linux-next memleak after IO on dax mountpoint

Hi, Reporting an oom/memleak issue in linux-next tree: #Description: dbench invokes oom-killer, make host unavaiable. dbench was doing IO on nvdimm device mounted fs with dax mount option. It happens on both xfs and ext4 filesystems. It does not happen testing without dax mountoption. Seems

linux-next memleak after IO on dax mountpoint

Hi, Reporting an oom/memleak issue in linux-next tree: #Description: dbench invokes oom-killer, make host unavaiable. dbench was doing IO on nvdimm device mounted fs with dax mount option. It happens on both xfs and ext4 filesystems. It does not happen testing without dax mountoption. Seems