Messages in this thread | | | Date | Mon, 18 Jun 2018 17:16:58 +0100 | From | Al Viro <> | Subject | Re: [PATCH] sg, bsg: mitigate read/write abuse, block uaccess in release |
| |
On Mon, Jun 18, 2018 at 09:37:01AM -0600, Jens Axboe wrote:
> > The folks responsible are no longer active in kernel development *** > > but as far as I know the async write(command), read(response) were > > added to bsg over 10 years ago as proof-of-concept and never properly > > worked in this async mode. The biggest design problem with it that I'm > > It was born with that mode, but I don't think anyone ever really used it. > So it might feasible to simply yank it. That said, just doing a prune > mode at ->release() time doesn't seem like such a hard task.
"prune mode" being...?
| |