Re: [PATCH v2 2/2] io_uring: Potential Oops in io_sq_offload_start()

To: "David S. Miller" <davem@xxxxxxxxxxxxx>, Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>, Jens Axboe <axboe@xxxxxxxxx>
Subject: Re: [PATCH v2 2/2] io_uring: Potential Oops in io_sq_offload_start()
From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Date: Tue, 30 Apr 2019 12:26:19 +0300
Cc: Amritha Nambiar <amritha.nambiar@xxxxxxxxx>, Willem de Bruijn <willemb@xxxxxxxxxx>, kernel-janitors@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Peter Zijlstra <peterz@xxxxxxxxxxxxx>
In-reply-to: <20190408081513.GB15239@kadam>
References: <20190404104527.GX4038@hirez.programming.kicks-ass.net> <20190408081513.GB15239@kadam>
User-agent: Mutt/1.9.4 (2018-02-28)

The io_uring patches are slated for v5.7 so we should figure out a
solution for this bug.

regrds,
dan carpenter

Follow-Ups:
- Re: [PATCH v2 2/2] io_uring: Potential Oops in io_sq_offload_start()
  - From: Dan Carpenter

References:
- Re: [PATCH 1/2] cpumask: Introduce possible_cpu_safe()
  - From: Peter Zijlstra
- [PATCH v2 2/2] io_uring: Potential Oops in io_sq_offload_start()
  - From: Dan Carpenter