xfs: fixes for for-next
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 11 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | xfs: don't leak EFSBADCRC to userspacefs/ fs/ fs/ | +18 | 10 replies | |
| 2/2 | xfs: use NOIO contexts for vm_map_ramfs/ fs/ | +31 | 1 reply |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Brian Foster | Christoph Hellwig |
|---|---|---|
| 1/2 | R-b | |
| 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] xfs: fixes for for-next
Hi folks,
A couple of quick fixes - the new verifier code leaks EFSBADCRC to userspace, so any code that is checking for EFSCORRUPTED is not going to be working correctly. The first patch fixes this regression.
The second patch fixes a long standing issues with vmapped RAM potentially causing deadlocks due to GFP_KERNEL allocations being done for page tables inside GFP_NOFS contexts. This will fix many of the lockdep reports about it, but won't get rid of them all. It will, however, guarantee that we won't deadlock due to the problem which is a big step up.
Cheers,
Dave.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs