On Sat, Jul 23, 2016 at 04:00:39PM +0200, Vegard Nossum wrote:
> On 07/23/2016 03:39 PM, Marcelo Ricardo Leitner wrote:
> > On Sat, Jul 23, 2016 at 11:52:23AM +0200, Vegard Nossum wrote:
> > > seq_read() can call ->start() twice on the same iterator more than once
> > > (e.g. once through traverse(
On 07/23/2016 03:39 PM, Marcelo Ricardo Leitner wrote:
On Sat, Jul 23, 2016 at 11:52:23AM +0200, Vegard Nossum wrote:
seq_read() can call ->start() twice on the same iterator more than once
(e.g. once through traverse() and once in seq_read() itself).
But when traverse() returns the error, it
On Sat, Jul 23, 2016 at 11:52:23AM +0200, Vegard Nossum wrote:
> seq_read() can call ->start() twice on the same iterator more than once
> (e.g. once through traverse() and once in seq_read() itself).
But when traverse() returns the error, it goes to Done label, skipping
the call to ->start() from
seq_read() can call ->start() twice on the same iterator more than once
(e.g. once through traverse() and once in seq_read() itself).
We should initialize sctp_ht_iter::start_fail to zero if ->start()
succeeds, otherwise it's possible that we leave an old value of 1 there,
which will cause ->stop(
