public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+921ef0ccfeed3a496721@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: memory leak in path_openat (2)
Date: Wed, 17 Feb 2021 05:41:19 +0000	[thread overview]
Message-ID: <YCysfxN1qQoalEJH@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <00000000000049fbd305bb816399@google.com>

On Tue, Feb 16, 2021 at 09:21:14PM -0800, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    dcc0b490 Merge tag 'powerpc-5.11-8' of git://git.kernel.or..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1316c614d00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=a2fbb1a71525e1d5
> dashboard link: https://syzkaller.appspot.com/bug?extid=921ef0ccfeed3a496721
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1378ba4cd00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12e73fc2d00000
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+921ef0ccfeed3a496721@syzkaller.appspotmail.com

Some observations:
	* .config is x86 one
	* merge in question is ppc-only
	* at least some "leaks" reported are dentries in devtmpfs,
	  which should stay around until the shutdown
Care to bisect to something more useful?

      reply	other threads:[~2021-02-17  5:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17  5:21 memory leak in path_openat (2) syzbot
2021-02-17  5:41 ` Al Viro [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=YCysfxN1qQoalEJH@zeniv-ca.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+921ef0ccfeed3a496721@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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