All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH 01/13] libnvdimm, pfn: fix nvdimm_namespace_add_poison() vs section alignment
Date: Thu, 24 Mar 2016 07:48:07 -0700	[thread overview]
Message-ID: <CAPcyv4i+7=k8AEtcq_7XyktQMaAbQzy3ezvxj_ziLDakwwotiw@mail.gmail.com> (raw)
In-Reply-To: <2305610.tLOzfXxl0W@c203>

On Thu, Mar 24, 2016 at 3:10 AM, Johannes Thumshirn <jthumshirn@suse.de> 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@intel.com>
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
>
> 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.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 01/13] libnvdimm, pfn: fix nvdimm_namespace_add_poison() vs section alignment
Date: Thu, 24 Mar 2016 07:48:07 -0700	[thread overview]
Message-ID: <CAPcyv4i+7=k8AEtcq_7XyktQMaAbQzy3ezvxj_ziLDakwwotiw@mail.gmail.com> (raw)
In-Reply-To: <2305610.tLOzfXxl0W@c203>

On Thu, Mar 24, 2016 at 3:10 AM, Johannes Thumshirn <jthumshirn@suse.de> 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@intel.com>
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
>
> 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.

WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 01/13] libnvdimm, pfn: fix nvdimm_namespace_add_poison() vs section alignment
Date: Thu, 24 Mar 2016 07:48:07 -0700	[thread overview]
Message-ID: <CAPcyv4i+7=k8AEtcq_7XyktQMaAbQzy3ezvxj_ziLDakwwotiw@mail.gmail.com> (raw)
In-Reply-To: <2305610.tLOzfXxl0W@c203>

On Thu, Mar 24, 2016 at 3:10 AM, Johannes Thumshirn <jthumshirn@suse.de> 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@intel.com>
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
>
> 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.

  reply	other threads:[~2016-03-24 14:49 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24  1:25 [PATCH 00/13] prep for device-dax, untangle pfn-device setup Dan Williams
2016-03-24  1:25 ` Dan Williams
2016-03-24  1:25 ` Dan Williams
2016-03-24  1:25 ` [PATCH 01/13] libnvdimm, pfn: fix nvdimm_namespace_add_poison() vs section alignment Dan Williams
2016-03-24  1:25   ` Dan Williams
2016-03-24  1:25   ` Dan Williams
2016-03-24 10:10   ` Johannes Thumshirn
2016-03-24 10:10     ` Johannes Thumshirn
2016-03-24 10:10     ` Johannes Thumshirn
2016-03-24 14:48     ` Dan Williams [this message]
2016-03-24 14:48       ` Dan Williams
2016-03-24 14:48       ` Dan Williams
2016-03-24  1:25 ` [PATCH 02/13] libnvdimm, pmem: kill pmem->ndns Dan Williams
2016-03-24  1:25   ` Dan Williams
2016-03-24 10:31   ` Johannes Thumshirn
2016-03-24 10:31     ` Johannes Thumshirn
2016-03-24  1:25 ` [PATCH 03/13] libnvdimm, pfn, convert nd_pfn_probe() to devm Dan Williams
2016-03-24  1:25   ` Dan Williams
2016-03-24 10:45   ` Johannes Thumshirn
2016-03-24 10:45     ` Johannes Thumshirn
2016-03-24  1:25 ` [PATCH 04/13] libnvdimm, btt, convert nd_btt_probe() " Dan Williams
2016-03-24  1:25   ` Dan Williams
2016-03-24 11:05   ` Johannes Thumshirn
2016-03-24 11:05     ` Johannes Thumshirn
2016-03-24  1:25 ` [PATCH 05/13] libnvdimm, blk: use devm_add_action to release bdev resources Dan Williams
2016-03-24  1:25   ` Dan Williams
2016-03-24 11:48   ` Johannes Thumshirn
2016-03-24 11:48     ` Johannes Thumshirn
2016-03-24 15:14     ` Dan Williams
2016-03-24 15:14       ` Dan Williams
2016-03-24 15:15       ` Johannes Thumshirn
2016-03-24 15:15         ` Johannes Thumshirn
2016-03-24 15:21         ` Dan Williams
2016-03-24 15:21           ` Dan Williams
2016-03-24  1:25 ` [PATCH 06/13] libnvdimm, blk: use ->queuedata for driver private data Dan Williams
2016-03-24  1:25   ` Dan Williams
2016-03-24 11:51   ` Johannes Thumshirn
2016-03-24 11:51     ` Johannes Thumshirn
2016-03-24  1:25 ` [PATCH 07/13] libnvdimm, pmem: " Dan Williams
2016-03-24  1:25   ` Dan Williams
2016-03-24 12:06   ` Johannes Thumshirn
2016-03-24 12:06     ` Johannes Thumshirn
2016-03-24  1:26 ` [PATCH 08/13] libnvdimm, blk: move i/o infrastructure to nd_namespace_blk Dan Williams
2016-03-24  1:26   ` Dan Williams
2016-03-24 12:22   ` Johannes Thumshirn
2016-03-24 12:22     ` Johannes Thumshirn
2016-03-24 15:21     ` Dan Williams
2016-03-24 15:21       ` Dan Williams
2016-03-24 15:22       ` Johannes Thumshirn
2016-03-24 15:22         ` Johannes Thumshirn
2016-03-25 22:02   ` [PATCH v2] " Dan Williams
2016-03-25 22:02     ` Dan Williams
2016-03-24  1:26 ` [PATCH 09/13] libnvdimm, pmem: use devm_add_action to release bdev resources Dan Williams
2016-03-24  1:26   ` Dan Williams
2016-03-24 12:35   ` Johannes Thumshirn
2016-03-24 12:35     ` Johannes Thumshirn
2016-03-24  1:26 ` [PATCH 10/13] libnvdimm, pmem: clean up resource print / request Dan Williams
2016-03-24  1:26   ` Dan Williams
2016-03-24 13:42   ` Johannes Thumshirn
2016-03-24 13:42     ` Johannes Thumshirn
2016-03-24  1:26 ` [PATCH 11/13] libnvdimm, pmem, pfn: make pmem_rw_bytes generic and refactor pfn setup Dan Williams
2016-03-24  1:26   ` Dan Williams
2016-03-24 13:50   ` Johannes Thumshirn
2016-03-24 13:50     ` Johannes Thumshirn
2016-03-25 22:13   ` [PATCH v2] " Dan Williams
2016-03-25 22:13     ` Dan Williams
2016-03-24  1:26 ` [PATCH 12/13] libnvdimm, pmem, pfn: move pfn setup to the core Dan Williams
2016-03-24  1:26   ` Dan Williams
2016-03-24 14:36   ` Johannes Thumshirn
2016-03-24 14:36     ` Johannes Thumshirn
2016-03-24 15:26     ` Dan Williams
2016-03-24 15:26       ` Dan Williams
2016-03-25 22:15   ` [PATCH v2] " Dan Williams
2016-03-25 22:15     ` Dan Williams
2016-03-29  8:30     ` Johannes Thumshirn
2016-03-29  8:30       ` Johannes Thumshirn
2016-03-24  1:26 ` [PATCH 13/13] libnvdimm, pmem: kill ->pmem_queue and ->pmem_disk Dan Williams
2016-03-24  1:26   ` Dan Williams
2016-03-24 14:38   ` Johannes Thumshirn
2016-03-24 14:38     ` Johannes Thumshirn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPcyv4i+7=k8AEtcq_7XyktQMaAbQzy3ezvxj_ziLDakwwotiw@mail.gmail.com' \
    --to=dan.j.williams@intel.com \
    --cc=jthumshirn@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.