aio: intialize kiocb private
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | orangefs: remove two un-needed BUG_ONs...fs/ | +0 | 2 replies | |
| 2/2 | aio: initialize kiocb private in case any filesystems expect it.fs/ | +1 | 1 reply |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Christoph Hellwig |
|---|---|
| 1/2 | |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] aio: intialize kiocb private
From: Mike Marshall <[email protected]>
"aio: don't zero entire aio_kiocb aio_get_req" triggered these BUG_ONs in orangefs file.c. Obviously the BUG_ONs need to go.
There might be other filesystems that use iocb->private without failing in a way that is as obvious as BUG_ON, though I didn't see any with grep.
After discussion on fsdevel, Jens Axboe suggested I should send in a patch that continues to set iocb->private to NULL just in case.
Also... phooey on fighting gmail when trying to send patches with git-send-email... mail.kernel.org works great!
-Mike