On 2017/3/9 5:39, Jaegeuk Kim wrote:
> On 03/08, Chao Yu wrote:
>> On 2017/3/7 5:51, Jaegeuk Kim wrote:
>>> This patch fixes that SSR can overwrite previous warm node block consisting
>>> of
>>> a node chain since the last checkpoint.
>>
>> Good catch!
>>
>> Need to consider the impact to other
On 2017/3/9 5:39, Jaegeuk Kim wrote:
> On 03/08, Chao Yu wrote:
>> On 2017/3/7 5:51, Jaegeuk Kim wrote:
>>> This patch fixes that SSR can overwrite previous warm node block consisting
>>> of
>>> a node chain since the last checkpoint.
>>
>> Good catch!
>>
>> Need to consider the impact to other
On 03/08, Chao Yu wrote:
> On 2017/3/7 5:51, Jaegeuk Kim wrote:
> > This patch fixes that SSR can overwrite previous warm node block consisting
> > of
> > a node chain since the last checkpoint.
>
> Good catch!
>
> Need to consider the impact to other accesser, e.g. is_checkpointed_data,
>
On 03/08, Chao Yu wrote:
> On 2017/3/7 5:51, Jaegeuk Kim wrote:
> > This patch fixes that SSR can overwrite previous warm node block consisting
> > of
> > a node chain since the last checkpoint.
>
> Good catch!
>
> Need to consider the impact to other accesser, e.g. is_checkpointed_data,
>
On 2017/3/7 5:51, Jaegeuk Kim wrote:
> This patch fixes that SSR can overwrite previous warm node block consisting of
> a node chain since the last checkpoint.
Good catch!
Need to consider the impact to other accesser, e.g. is_checkpointed_data,
add_discard_addrs?
Thanks,
>
> Fixes:
On 2017/3/7 5:51, Jaegeuk Kim wrote:
> This patch fixes that SSR can overwrite previous warm node block consisting of
> a node chain since the last checkpoint.
Good catch!
Need to consider the impact to other accesser, e.g. is_checkpointed_data,
add_discard_addrs?
Thanks,
>
> Fixes:
6 matches
Mail list logo