From: Ian Kent <raven@themaw.net>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Matthew Wilcox <willy@infradead.org>,
Andrei Vagin <avagin@gmail.com>,
Takeshi Misawa <jeliantsurux@gmail.com>,
autofs@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexey Khoroshilov <khoroshilov@ispras.ru>,
lvc-project@linuxtesting.org
Subject: Re: [PATCH 0/1] autofs: fix memory leak of waitqueues in autofs_catatonic_mode
Date: Mon, 13 Feb 2023 12:27:55 +0800 [thread overview]
Message-ID: <5b86f03b-020b-1584-be8f-b7dc7277fa0a@themaw.net> (raw)
In-Reply-To: <20230211195950.452364-1-pchelkin@ispras.ru>
On 12/2/23 03:59, Fedor Pchelkin wrote:
> Syzkaller reports the leak [1]. It is reproducible.
>
> The following patch fixes the leak. It was proposed by Takeshi Misawa and
> tested by Syzbot.
>
> In other places of the code the waitqueue is freed when its wait_ctr
> becomes zero (see autofs_wait_release). So I think it is not actually
> supposed that inside autofs_catatonic_mode wait_ctr cannot be decreased to
> zero. Please correct me if I'm wrong.
This is a bit had to read but I think your saying there's an assumption
that wait_ctr can't become zero in autofs_catatonic_mode().
That's correct, the case of a waiting process getting sent a signal is
not accounted for and this can (as you observed) lead to the wait not
being freed and also not being freed at umount.
I think the change here should be sufficient to resolve the leak and
I can't think of any cases where this could cause a further problem.
>
> Also, looking at the discussion [2] of the '[PATCH] autofs4: use wake_up()
> instead of wake_up_interruptible', shouldn't wake_up_interruptible()
> inside autofs_catatonic_mode() be replaced with wake_up()?
This does imply that [2] should have been applied to autofs_catatonic_mode()
as well, I'm still trying to grok if that change would cause side effects
for the change here but I think not.
Ian
next prev parent reply other threads:[~2023-02-13 4:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 19:59 Fedor Pchelkin
2023-02-11 19:59 ` [PATCH 1/1] " Fedor Pchelkin
2023-02-13 1:25 ` [PATCH 0/1] " Ian Kent
2023-02-13 4:27 ` Ian Kent [this message]
2023-02-13 4:37 ` Ian Kent
2023-03-10 17:56 ` Fedor Pchelkin
2023-03-11 7:01 ` Ian Kent
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=5b86f03b-020b-1584-be8f-b7dc7277fa0a@themaw.net \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=avagin@gmail.com \
--cc=jeliantsurux@gmail.com \
--cc=khoroshilov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
--cc=willy@infradead.org \
/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
all inboxes | Powered by JetHome®