linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+942d5390db2d9624ced8@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	miklos@szeredi.hu, syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: [syzbot] memory leak in cap_inode_getsecurity
Date: Tue, 02 Aug 2022 21:53:07 -0700	[thread overview]
Message-ID: <0000000000004a9f7b05e54f0213@google.com> (raw)
In-Reply-To: <CAJfpeguS6Ta9LcGU0A_JkfvPWZup_Ndg+tpvpbzXJuWPNZwGgw@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+942d5390db2d9624ced8@syzkaller.appspotmail.com

Tested on:

commit:         e2b54210 Merge tag 'flexible-array-transformations-UAP..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12c050a2080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f5367bd9b8d9fa72
dashboard link: https://syzkaller.appspot.com/bug?extid=942d5390db2d9624ced8
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch:          https://syzkaller.appspot.com/x/patch.diff?x=17a74536080000

Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2022-08-03  4:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 19:59 memory leak in cap_inode_getsecurity syzbot
2022-07-31 15:12 ` [syzbot] " syzbot
2022-08-01 10:11   ` Miklos Szeredi
2022-08-01 10:29     ` syzbot
2022-08-01 12:20   ` Miklos Szeredi
2022-08-01 12:37     ` syzbot
2022-08-03  4:36 ` Miklos Szeredi
2022-08-03  4:53   ` syzbot [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=0000000000004a9f7b05e54f0213@google.com \
    --to=syzbot+942d5390db2d9624ced8@syzkaller.appspotmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).