Dan Williams writes:
> At namespace creation time there is the potential for the "expected to
> be zero" fields of a 'pfn' info-block to be filled with indeterminate
> data. While the kernel buffer is zeroed on allocation it is immediately
> overwritten by nd_pfn_validate() filling it with the cu
On Fri, Jun 7, 2019 at 12:54 PM Andrew Morton wrote:
>
> On Thu, 6 Jun 2019 15:06:26 -0700 Dan Williams
> wrote:
>
> > On Thu, Jun 6, 2019 at 2:46 PM Andrew Morton
> > wrote:
> > >
> > > On Wed, 05 Jun 2019 14:58:58 -0700 Dan Williams
> > > wrote:
> > >
> > > > At namespace creation time the
On Thu, 6 Jun 2019 15:06:26 -0700 Dan Williams wrote:
> On Thu, Jun 6, 2019 at 2:46 PM Andrew Morton
> wrote:
> >
> > On Wed, 05 Jun 2019 14:58:58 -0700 Dan Williams
> > wrote:
> >
> > > At namespace creation time there is the potential for the "expected to
> > > be zero" fields of a 'pfn' in
On Thu, Jun 6, 2019 at 2:46 PM Andrew Morton wrote:
>
> On Wed, 05 Jun 2019 14:58:58 -0700 Dan Williams
> wrote:
>
> > At namespace creation time there is the potential for the "expected to
> > be zero" fields of a 'pfn' info-block to be filled with indeterminate
> > data. While the kernel buffe
On Wed, 05 Jun 2019 14:58:58 -0700 Dan Williams
wrote:
> At namespace creation time there is the potential for the "expected to
> be zero" fields of a 'pfn' info-block to be filled with indeterminate
> data. While the kernel buffer is zeroed on allocation it is immediately
> overwritten by nd_pf
At namespace creation time there is the potential for the "expected to
be zero" fields of a 'pfn' info-block to be filled with indeterminate
data. While the kernel buffer is zeroed on allocation it is immediately
overwritten by nd_pfn_validate() filling it with the current contents of
the on-media
6 matches
Mail list logo