From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Snitzer Subject: Re: [4.7.0rc6] Page Allocation Failures with dm-crypt Date: Mon, 11 Jul 2016 09:44:54 -0400 Message-ID: <20160711134454.GA28370@redhat.com> References: <28dc911645dce0b5741c369dd7650099@mail.ud19.udmedia.de> <20160711131818.GA28102@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org To: Matthias Dahl Cc: linux-mm@kvack.org, dm-devel@redhat.com, linux-kernel@vger.kernel.org List-Id: dm-devel.ids On Mon, Jul 11 2016 at 9:27am -0400, Matthias Dahl wrote: > Hello Mike... > > On 2016-07-11 15:18, Mike Snitzer wrote: > > >Something must explain the execessive nature of your leak but > >it isn't a known issue. > > Since I am currently setting up the new machine, all tests were > performed w/ various live cd images (Fedora Rawhide, Gentoo, ...) > and I saw the exact same behavior everywhere. > > >Have you tried running with kmemleak enabled? > > I would have to check if that is enabled on the live images but even if > it is, how would that work? The default interval is 10min. If I fire up > a dd, the memory is full within two seconds or so... and after that, the > OOM killer kicks in and all hell breaks loose unfortunately. You can control when kmemleak scans. See Documentation/kmemleak.txt You could manually trigger a scan just after the dd is started. But I doubt the livecds have kmemleak compiled into their kernels. > I don't think this is a particular unique issue on my side. You could, > if I am right, easily try a Fedora Rawhide image and reproduce it there > yourself. The only unique point here is my RAID10 which is a Intel Rapid > Storage s/w RAID. I have no clue if this could indeed cause such a "bug" > and how. What is your raid10's full stripesize? Is your dd IO size of 512K somehow triggering excess R-M-W cycles which is exacerbating the problem? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030377AbcGKNo5 (ORCPT ); Mon, 11 Jul 2016 09:44:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56655 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751565AbcGKNo4 (ORCPT ); Mon, 11 Jul 2016 09:44:56 -0400 Date: Mon, 11 Jul 2016 09:44:54 -0400 From: Mike Snitzer To: Matthias Dahl Cc: linux-mm@kvack.org, dm-devel@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [4.7.0rc6] Page Allocation Failures with dm-crypt Message-ID: <20160711134454.GA28370@redhat.com> References: <28dc911645dce0b5741c369dd7650099@mail.ud19.udmedia.de> <20160711131818.GA28102@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Mon, 11 Jul 2016 13:44:55 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 11 2016 at 9:27am -0400, Matthias Dahl wrote: > Hello Mike... > > On 2016-07-11 15:18, Mike Snitzer wrote: > > >Something must explain the execessive nature of your leak but > >it isn't a known issue. > > Since I am currently setting up the new machine, all tests were > performed w/ various live cd images (Fedora Rawhide, Gentoo, ...) > and I saw the exact same behavior everywhere. > > >Have you tried running with kmemleak enabled? > > I would have to check if that is enabled on the live images but even if > it is, how would that work? The default interval is 10min. If I fire up > a dd, the memory is full within two seconds or so... and after that, the > OOM killer kicks in and all hell breaks loose unfortunately. You can control when kmemleak scans. See Documentation/kmemleak.txt You could manually trigger a scan just after the dd is started. But I doubt the livecds have kmemleak compiled into their kernels. > I don't think this is a particular unique issue on my side. You could, > if I am right, easily try a Fedora Rawhide image and reproduce it there > yourself. The only unique point here is my RAID10 which is a Intel Rapid > Storage s/w RAID. I have no clue if this could indeed cause such a "bug" > and how. What is your raid10's full stripesize? Is your dd IO size of 512K somehow triggering excess R-M-W cycles which is exacerbating the problem?