Re: [PATCH 1/2] debugfs: prevent access to possibly dead file_operations at file open

2016-02-07 Thread Greg Kroah-Hartman
On Tue, Dec 01, 2015 at 12:21:31AM +0100, Nicolai Stange wrote: > Nothing prevents a dentry found by path lookup before a return of > __debugfs_remove() to actually get opened after that return. Now, after > the return of __debugfs_remove(), there are no guarantees whatsoever > regarding the memory

Re: [PATCH 1/2] debugfs: prevent access to possibly dead file_operations at file open

2015-12-01 Thread Nicolai Stange
"Paul E. McKenney" writes: > On Tue, Dec 01, 2015 at 12:21:31AM +0100, Nicolai Stange wrote: >> Nothing prevents a dentry found by path lookup before a return of >> __debugfs_remove() to actually get opened after that return. Now, after >> the return of __debugfs_remove(), there are no guarantees

Re: [PATCH 1/2] debugfs: prevent access to possibly dead file_operations at file open

2015-12-01 Thread Paul E. McKenney
On Tue, Dec 01, 2015 at 12:21:31AM +0100, Nicolai Stange wrote: > Nothing prevents a dentry found by path lookup before a return of > __debugfs_remove() to actually get opened after that return. Now, after > the return of __debugfs_remove(), there are no guarantees whatsoever > regarding the memory

Re: [PATCH 1/2] debugfs: prevent access to possibly dead file_operations at file open

2015-11-30 Thread Greg Kroah-Hartman
On Tue, Dec 01, 2015 at 12:21:31AM +0100, Nicolai Stange wrote: > Nothing prevents a dentry found by path lookup before a return of > __debugfs_remove() to actually get opened after that return. Now, after > the return of __debugfs_remove(), there are no guarantees whatsoever > regarding the memory

[PATCH 1/2] debugfs: prevent access to possibly dead file_operations at file open

2015-11-30 Thread Nicolai Stange
Nothing prevents a dentry found by path lookup before a return of __debugfs_remove() to actually get opened after that return. Now, after the return of __debugfs_remove(), there are no guarantees whatsoever regarding the memory the corresponding inode's file_operations object had been kept in. Sin