On Sat 19-01-19 08:09:34, Michal Hocko wrote:
[...]
> Fixes: 5e9d834a0e0c ("oom: sacrifice child with highest badness score for
> parent")
So I've double checked and I was wrong blaming this commit. Back then it
was tasklist_lock to protect us from releasing the task. It's been only
since
On Fri, Jan 18, 2019 at 5:58 PM Roman Gushchin wrote:
>
> Hi Shakeel!
>
> >
> > On looking further it seems like the process selected to be oom-killed
> > has exited even before reaching read_lock(_lock) in
> > oom_kill_process(). More specifically the tsk->usage is 1 which is due
> > to
On Fri, Jan 18, 2019 at 11:09 PM Michal Hocko wrote:
>
> On Fri 18-01-19 16:50:22, Shakeel Butt wrote:
> [...]
> > On looking further it seems like the process selected to be oom-killed
> > has exited even before reaching read_lock(_lock) in
> > oom_kill_process(). More specifically the
On Fri, Jan 18, 2019 at 7:35 PM Tetsuo Handa
wrote:
>
> On 2019/01/19 9:50, Shakeel Butt wrote:
> > On looking further it seems like the process selected to be oom-killed
> > has exited even before reaching read_lock(_lock) in
> > oom_kill_process(). More specifically the tsk->usage is 1 which is
On Fri 18-01-19 16:50:22, Shakeel Butt wrote:
[...]
> On looking further it seems like the process selected to be oom-killed
> has exited even before reaching read_lock(_lock) in
> oom_kill_process(). More specifically the tsk->usage is 1 which is due
> to get_task_struct() in oom_evaluate_task()
On 2019/01/19 9:50, Shakeel Butt wrote:
> On looking further it seems like the process selected to be oom-killed
> has exited even before reaching read_lock(_lock) in
> oom_kill_process(). More specifically the tsk->usage is 1 which is due
> to get_task_struct() in oom_evaluate_task() and the
Hi Shakeel!
>
> On looking further it seems like the process selected to be oom-killed
> has exited even before reaching read_lock(_lock) in
> oom_kill_process(). More specifically the tsk->usage is 1 which is due
> to get_task_struct() in oom_evaluate_task() and the put_task_struct
> within
In our internal syzbot instance running on upstream kernel, we see the
following crash.
syzbot has found the following crash on:
HEAD commit: 47bfa6d9dc8c Merge tag 'selinux-pr-20190115' of
git://git.kernel.org/pub/scm/linux/kernel/g..
git tree:
8 matches
Mail list logo