On Thu, Mar 24, 2016 at 3:10 AM, Johannes Thumshirn <jthumshirn@xxxxxxx> wrote: > On Mittwoch, 23. März 2016 18:25:26 CET Dan Williams wrote: >> When section alignment padding is in effect we need to shift / truncate >> the range that is queried for poison by the 'start_pad' or 'end_trunc' >> reservations. >> >> It's easiest if we just pass in an adjusted resource range rather than >> deriving it from the passed in namespace. With the resource range >> resolution pushed out to the caller we can also push the >> namespace-to-region lookup to the caller and drop the implicit pmem-type >> assumption about the passed in namespace object. >> >> Cc: Vishal Verma <vishal.l.verma@xxxxxxxxx> >> Cc: <stable@xxxxxxxxxxxxxxx> >> Signed-off-by: Dan Williams <dan.j.williams@xxxxxxxxx> > > Does this really qualify for inclusion into stable? Depends on when we push it. If we wait for the 4.7 merge window this will be -stable material to fix 4.6. The lack of urgency is driven by the fact that there is still time to work with BIOS implementations to address the 128MB alignment problem. -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html