Only reduce __zio_execute() stack usage in kernel space

Related to 91579709fccd3e55a21970742b66c388fb1403db we need to
be very careful about not overrunning the stack in kernel space.
However, in user space we're already allowing slightly larger
stacks so this stack usage optimization is not required there.

Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>

diff --git a/module/zfs/zio.c b/module/zfs/zio.c
index 638105a098dfd52b64a4d118a4cc80bb5ebbdb06..dab417c206ba2c95f938634a4e0f91a4ee5cbd42 100644 (file)
--- a/module/zfs/zio.c
+++ b/module/zfs/zio.c
@@ -1281,6 +1281,7 @@ __zio_execute(zio_t *zio)
                        return;
                }
 
+#ifdef _KERNEL
                /*
                 * If we executing in the context of the tx_sync_thread,
                 * or we are performing pool initialization outside of a
@@ -1293,6 +1294,7 @@ __zio_execute(zio_t *zio)
                        zio_taskq_dispatch(zio, ZIO_TASKQ_ISSUE, cut);
                        return;
                }
+#endif
 
                zio->io_stage = stage;
                rv = zio_pipeline[highbit(stage) - 1](zio);