[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <153805773703.1157.14773321497580233478.stgit@bhelgaas-glaptop.roam.corp.google.com>
Date: Thu, 27 Sep 2018 09:21:49 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: linux-kernel@...r.kernel.org
Cc: Lianbo Jiang <lijiang@...hat.com>, Vivek Goyal <vgoyal@...hat.com>,
kexec@...ts.infradead.org, tglx@...utronix.de, mingo@...hat.com,
hpa@...or.com, x86@...nel.org, akpm@...ux-foundation.org,
dan.j.williams@...el.com, thomas.lendacky@....com,
baiyaowei@...s.chinamobile.com, tiwai@...e.de, bp@...e.de,
brijesh.singh@....com, dyoung@...hat.com, bhe@...hat.com
Subject: [PATCH 0/3] find_next_iomem_res() fixes
These fix:
- A kexec off-by-one error that we probably never see in practice (only
affects a resource starting at exactly 640KB).
- A corner case in walk_iomem_res_desc(), walk_system_ram_res(), etc that
we probably also never see in practice (only affects a single byte
resource at the very end of the region we're searching)
- An issue in walk_iomem_res_desc() that apparently causes a kdump issue
(see Lianbo's note at [1]).
I think we need to fix the kdump issue either by these patches
(specifically the last one) or by the patch Lianbo posted [2].
I'm hoping to avoid deciding and merging these myself, but I'm not
sure who really wants to own kernel/resource.c.
[1] https://lore.kernel.org/lkml/01551d06-c421-5df3-b19f-fc66f3639e4f@redhat.com
[2] https://lore.kernel.org/lkml/20180921073211.20097-2-lijiang@redhat.com
---
Bjorn Helgaas (3):
x86/kexec: Correct KEXEC_BACKUP_SRC_END off-by-one error
resource: Include resource end in walk_*() interfaces
resource: Fix find_next_iomem_res() iteration issue
arch/x86/include/asm/kexec.h | 2 -
kernel/resource.c | 96 ++++++++++++++++++------------------------
2 files changed, 43 insertions(+), 55 deletions(-)
Powered by blists - more mailing lists