Re: [linux-next] BUG triggered in ptraceme

2018-09-27 Thread Cyrill Gorcunov
On Thu, Sep 27, 2018 at 05:35:10PM +0200, Jann Horn wrote: ... > > > > Lets wait for fs people opinions. > > No reply yet - I guess I should just fix up the traceme case for now. Yes please.

Re: [linux-next] BUG triggered in ptraceme

2018-09-27 Thread Jann Horn
On Wed, Sep 19, 2018 at 6:13 PM Cyrill Gorcunov wrote: > > On Wed, Sep 19, 2018 at 04:16:50PM +0200, Jann Horn wrote: > ... > > > > > > Heh, actually not :) It is due to commit > > > > > > commit 1f8266ff58840d698a1e96d2274189de1bdf7969 > > > Author: Jann Horn > > > Date: Thu Sep 13 18:12:09 20

Re: [linux-next] BUG triggered in ptraceme

2018-09-19 Thread Cyrill Gorcunov
On Wed, Sep 19, 2018 at 04:16:50PM +0200, Jann Horn wrote: ... > > > > Heh, actually not :) It is due to commit > > > > commit 1f8266ff58840d698a1e96d2274189de1bdf7969 > > Author: Jann Horn > > Date: Thu Sep 13 18:12:09 2018 +0200 > > > > which introduced might_sleep. Seems it is bad idea to sen

Re: [linux-next] BUG triggered in ptraceme

2018-09-19 Thread Jann Horn
Adding FS people to figure out whether GFP_KERNEL allocations with i_rwsem's held for writing are okay. On Wed, Sep 19, 2018 at 9:10 AM Cyrill Gorcunov wrote: > On Wed, Sep 19, 2018 at 10:07:37AM +0300, Cyrill Gorcunov wrote: > > Hi Oleg! While been testing criu with linux-next we've triggered a

Re: [linux-next] BUG triggered in ptraceme

2018-09-19 Thread Cyrill Gorcunov
On Wed, Sep 19, 2018 at 10:07:37AM +0300, Cyrill Gorcunov wrote: > Hi Oleg! While been testing criu with linux-next we've triggered a BUG. > https://api.travis-ci.org/v3/job/430308998/log.txt > > [2.461618] BUG: sleeping function called from invalid context at > security/apparmor/include/cred