On Fri, Jan 9, 2026 at 6:19 PM Bobby Eshleman <[email protected]> wrote: > > From: Bobby Eshleman <[email protected]> > > Add test case for autorelease. > > The test case is the same as the RX test, but enables autorelease. The > original RX test is changed to use the -a 0 flag to disable autorelease. > > TAP version 13 > 1..4 > ok 1 devmem.check_rx > ok 2 devmem.check_rx_autorelease > ok 3 devmem.check_tx > ok 4 devmem.check_tx_chunks > > Signed-off-by: Bobby Eshleman <[email protected]>
Can you add a test for the problematic/weird scenario I comment on patch 3? 1. User does bind (autorelease on or off) 2. Data is received. 3. User does unbind. 4. User calls recevmsg() 5. User calls dontneed on the frags obtained in 4. This should work with autorelease=on or off, or at least emit a clean error message (kernel must not splat). I realize a made a suggestion in patch 3 that may make this hard to test (i.e. put the kernel in autorelease on/off mode for the boot session on the first unbind). If we can add a test while making that simplification great, if not, lets not make the simplification I guess.
