On Wed, 15 Jan 2014 12:47:00 -0800 Davidlohr Bueso <davidl...@hp.com> wrote:
> > Well, we're mainly looking for bugfixes this last in the cycle. > > "[PATCH v3 03/14] mm, hugetlb: protect region tracking via newly > > introduced resv_map lock" fixes a bug, but I'd assumed that it depended > > on earlier patches. > > It doesn't seem to depend on anything. All 1-7 patches apply cleanly on > linux-next, the last change to mm/hugetlb.c was commit 3ebac7fa (mm: > dump page when hitting a VM_BUG_ON using VM_BUG_ON_PAGE). > > > If we think that one is serious then it would be > > better to cook up a minimal fix which is backportable into 3.12 and > > eariler? > > I don't think it's too serious, afaik it's a theoretical race and I > haven't seen any bug reports for it. So we can probably just wait for > 3.14, as you say, it's already late in the cycle anyways. OK, thanks. > Just let me > know what you want to do so we can continue working on the actual > performance issue. A resend after -rc1 would suit. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
