From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Observation of a memory leak with commit 314001f0bf92 ("af_unix: Add OOB support") #forregzbot
Date: Mon, 10 Jan 2022 14:15:10 +0100 [thread overview]
Message-ID: <0408cc8b-c67f-ea28-8e82-8a7de57089ff@leemhuis.info> (raw)
In-Reply-To: <CAKXUXMzZkQvHJ35nwVhcJe+DrtEXGw+eKGVD04=xRJkVUC2sPA@mail.gmail.com>
On 07.01.22 07:48, Lukas Bulwahn wrote:
> Dear Rao and David,
>
>
> In our syzkaller instance running on linux-next,
> https://elisa-builder-00.iol.unh.edu/syzkaller-next/, we have been
> observing a memory leak in prepare_creds,
> https://elisa-builder-00.iol.unh.edu/syzkaller-next/report?id=1dcac8539d69ad9eb94ab2c8c0d99c11a0b516a3,
> for quite some time.
>
> It is reproducible on v5.15-rc1, v5.15, v5.16-rc8 and next-20220104.
> So, it is in mainline, was released and has not been fixed in
> linux-next yet.
>
> As syzkaller also provides a reproducer, we bisected this memory leak
> to be introduced with commit 314001f0bf92 ("af_unix: Add OOB
> support").
>
> We also tested that reverting this commit on torvalds' current tree
> made the memory leak with the reproducer go away.
>
> Could you please have a look how your commit introduces this memory
> leak? We will gladly support testing your fix in case help is needed.
#regzbot ^introduced: 314001f0bf92
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
prev parent reply other threads:[~2022-01-10 13:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 6:48 Observation of a memory leak with commit 314001f0bf92 ("af_unix: Add OOB support") Lukas Bulwahn
2022-01-07 17:54 ` Shoaib Rao
2022-01-09 4:10 ` Lukas Bulwahn
[not found] ` <20220109064905.1594-1-hdanton@sina.com>
2022-01-10 15:15 ` Lukas Bulwahn
2022-01-09 21:20 ` Jakub Kicinski
2022-01-10 14:02 ` Thorsten Leemhuis
2022-01-10 16:19 ` Lukas Bulwahn
2022-01-10 16:29 ` Jakub Kicinski
2022-01-28 13:17 ` Thorsten Leemhuis
2022-01-10 16:21 ` Jakub Kicinski
2022-01-10 14:54 ` Lukas Bulwahn
2022-01-10 13:15 ` Thorsten Leemhuis [this message]
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=0408cc8b-c67f-ea28-8e82-8a7de57089ff@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.