linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: Hillf Danton <hdanton@sina.com>
Cc: Munehisa Kamata <kamatam@amazon.com>,
	hannes@cmpxchg.org, ebiggers@kernel.org,  mengcc@amazon.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: another use-after-free in ep_remove_wait_queue()
Date: Mon, 9 Jan 2023 17:33:45 -0800	[thread overview]
Message-ID: <CAJuCfpEWd6RtevMiUcv7RCH7rjadTMr7UYjJJiGw1ReNHtbJ0g@mail.gmail.com> (raw)
In-Reply-To: <20230108234917.5322-1-hdanton@sina.com>

On Sun, Jan 8, 2023 at 3:49 PM Hillf Danton <hdanton@sina.com> wrote:
>
> On 8 Jan 2023 14:25:48 -0800 PM Munehisa Kamata <kamatam@amazon.com> wrote:
> >
> > That patch survived the repro in my original post, however, the waker
> > (rmdir) was getting stuck until a file descriptor of the epoll instance or
> > the pressure file got closed. So, if the following modified repro runs
> > with the patch, the waker never returns (unless the sleeper gets killed)
> > while holding cgroup_mutex. This doesn't seem to be what you expected to
> > see with the patch, does it? Even wake_up_all() does not appear to empty
> > the queue, but wake_up_pollfree() does.
>
> Thanks for your testing. And the debugging completes.
>
> Mind sending a patch with wake_up_pollfree() folded?

I finally had some time to look into this issue. I don't think
delaying destruction in psi_trigger_destroy() because there are still
users of the trigger as Hillf suggested is a good way to go. Before
[1] correct trigger destruction was handled using a
psi_trigger.refcount. For some reason I thought it's not needed
anymore when we placed one-trigger-per-file restriction in that patch,
so I removed it. Obviously that was a wrong move, so I think the
cleanest way would be to bring back the refcounting. That way the last
user of the trigger (either psi_trigger_poll() or psi_fop_release())
will free the trigger.
I'll check once more to make sure I did not miss anything and if there
are no objections, will post a fix.

[1] https://lore.kernel.org/lkml/20220111232309.1786347-1-surenb@google.com/

Thanks,
Suren.

>
> Hillf


  reply	other threads:[~2023-01-10  1:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230106224859.4123476-1-kamatam@amazon.com>
2023-01-07  8:07 ` Hillf Danton
2023-01-08 22:25   ` Munehisa Kamata
2023-01-08 23:49     ` Hillf Danton
2023-01-10  1:33       ` Suren Baghdasaryan [this message]
2023-01-10  3:06         ` Suren Baghdasaryan
2023-01-12 22:01           ` Suren Baghdasaryan
2023-01-13  2:25             ` Munehisa Kamata
2023-01-13 17:52               ` Suren Baghdasaryan
2023-01-19  3:06                 ` Suren Baghdasaryan
2023-01-19 21:01                   ` Suren Baghdasaryan
2023-01-19 22:25                     ` Johannes Weiner
2023-01-20  1:30                     ` Hillf Danton
2023-01-20  1:37                       ` Suren Baghdasaryan
2023-01-20  2:46                         ` Munehisa Kamata
2023-01-20  2:52                           ` Munehisa Kamata
2023-01-20  9:00                         ` Hillf Danton
2023-01-20 16:28                           ` Suren Baghdasaryan
2023-01-21  5:17                             ` Hillf Danton
2023-01-22  3:01                               ` Suren Baghdasaryan
2023-01-20  1:45                     ` Munehisa Kamata
2023-02-02  3:00                     ` [PATCH] sched/psi: fix " Munehisa Kamata
2023-02-02  4:56                       ` Eric Biggers
2023-02-02 21:11                         ` Suren Baghdasaryan
2023-02-09 17:09                           ` Suren Baghdasaryan
2023-02-09 18:46                             ` Eric Biggers
2023-02-09 19:13                               ` Suren Baghdasaryan
2023-02-13 23:50                                 ` Suren Baghdasaryan
2023-02-14  7:04                                   ` [PATCH v2] " Munehisa Kamata
2023-02-14 17:10                                     ` Suren Baghdasaryan
2023-02-14 18:13                                       ` [PATCH v3] " Munehisa Kamata
2023-02-14 18:28                                         ` Suren Baghdasaryan
2023-02-14 18:29                                           ` Suren Baghdasaryan
2023-02-14 18:55                                         ` Eric Biggers
2023-02-14 19:13                                           ` Suren Baghdasaryan
2023-02-14 18:37                                       ` [PATCH v2] " Munehisa Kamata

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJuCfpEWd6RtevMiUcv7RCH7rjadTMr7UYjJJiGw1ReNHtbJ0g@mail.gmail.com \
    --to=surenb@google.com \
    --cc=ebiggers@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=hdanton@sina.com \
    --cc=kamatam@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mengcc@amazon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox