fs: forbid to open anon-inode files via /proc
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | fs: forbid to open anon-inode files via /procfs/ | +8 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] fs: forbid to open anon-inode files via /proc
Quoted 17 lines · Oleg Nesterov
Quoted 15 lines · Oleg Nesterov
Quoted 10 lines · Stephen Rothwell
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
fs/anon_inodes.cbetween commit24b0303e9532("take anon inode allocation tolibfs.c") from the vfs tree and commit02f3ac4386d9("anon_inodefs:
forbid open via /proc") from the akpm-current tree.I just dropped the akpm-current changes for today - they should probably be applied to
fs/libfs.c.Well, this probably means that
Quoted 8 lines
Quoted 3 lines
anon_inodefs-forbid-open-via-proc.patch
should be dropped. I'll rediff this patch against vfs.git
24b0303e9532also removesanon_inode_fops. It seems that it was not really needed anyway,inode_init_always()doesinode->i_fop=empty_fops...So probably we can simply change
empty_fopsbut I need to recheck.
Well. It looks "really obvious" that any user of inode_init_always() either needs to change ->i_fop or this file should not be opened via /proc...
So, Al, feel free to ignore, this is minor. Still I think this patch makes sense. Based on vfs.git#for-next.
Oleg.