From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx205.postini.com [74.125.245.205]) by kanga.kvack.org (Postfix) with SMTP id 6DDDB6B0039 for ; Mon, 26 Aug 2013 16:46:06 -0400 (EDT) Received: by mail-vb0-f50.google.com with SMTP id x14so2379801vbb.23 for ; Mon, 26 Aug 2013 13:46:05 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20130807153030.GA25515@redhat.com> <20130819231836.GD14369@redhat.com> <20130821204901.GA19802@redhat.com> <20130823032127.GA5098@redhat.com> <20130823035344.GB5098@redhat.com> <20130826190757.GB27768@redhat.com> Date: Mon, 26 Aug 2013 13:46:05 -0700 Message-ID: Subject: Re: unused swap offset / bad page map. From: Linus Torvalds Content-Type: text/plain; charset=UTF-8 Sender: owner-linux-mm@kvack.org List-ID: To: Dave Jones , Hillf Danton , Linux-MM , Linux Kernel , Hugh Dickins On Mon, Aug 26, 2013 at 1:15 PM, Linus Torvalds wrote: > > So I'm almost likely to think that we are more likely to have > something wrong in the messy magical special cases. Of course, the good news would be if it actually ends up being the soft-dirty stuff, and bisection hits something recent. So maybe I'm overly pessimistic. That messy swap_map[] code really _is_ messy, but at the same time it should also be pretty well-tested. I don't think it's been touched in years. That said, google does find "swap_free: Unused swap offset entry" reports from over the years. Most of them seem to be single-bit errors, though (ie when the entry is 00000100 or similar I'm more inclined to blame a bit error - in contrast your values look like "real" swap entries). Linus -- 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