Paul Dagnelie da19d919a8 Fix incremental receive silently failing for recursive sends ...

The problem occurs because dmu_recv_begin pulls in the payload and 
next header from the input stream in order to use the contents of 
the begin record's nvlist. However, the change to do that before the 
other checks in dmu_recv_begin occur caused a regression where an 
empty send stream in a recursive send could have its END record 
consumed by this, which broke the logic of recv_skip. A test is 
also included to protect against this case in the future.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Paul Dagnelie <pcd@delphix.com>
Closes #12661
Closes #14568

2023-03-10 09:52:44 -08:00

..

common.run

Fix incremental receive silently failing for recursive sends

2023-03-10 09:52:44 -08:00

freebsd.run

Expose additional file level attributes

2022-03-07 17:52:03 -08:00

linux.run

Configure zed's diagnosis engine with vdev properties

2023-01-23 13:14:25 -08:00

longevity.run

OpenZFS 9166 - zfs storage pool checkpoint

2018-06-26 10:07:42 -07:00

perf-regression.run

OpenZFS 9184 - Add ZFS performance test for fixed blocksize random read/write IO

2018-07-02 13:46:06 -07:00

sanity.run

Wait for txg sync if the last DRR_FREEOBJECTS might result in a hole

2023-01-23 13:19:43 -08:00

sunos.run

ZTS: Add a failsafe callback to run after each test

2020-03-10 11:00:56 -07:00