From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f77.google.com (mail-oo1-f77.google.com [209.85.161.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 16156363C46 for ; Fri, 17 Apr 2026 13:37:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.77 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776433043; cv=none; b=TZEQoAZc3w8xBKYwywuSwnETFoh+onyVX/AWJuvhUriUnwrPdTPI8u6LEP4AH6Xuh6Jrphqzah+fduzQK384rxx/QhVVyM5CLVpYK/g9WYdbUD9zz4sarYhw3IZySeCMVVFcxz0J/Mq6/yFRnnQ2RzZfxVoHNbpUGkzrrZNkYng= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776433043; c=relaxed/simple; bh=U3+/j26jyD0jCPDtwRMMkl5wbWrWC5bhBKJAQGo+hH0=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=cnXHYRtNdF3hI8TOocO4aAFP5LHrWVM9wiL390luxLPyiYa8H1HBzcJo/I3F51MDlZD24UlCuj8A+swUnyjBgtjG4JD4NmZE+hsEli+3EDYC4OJRm+MOo2Mr2qoqWUIe+Sp2sOGIZGJm2WyQS8MSKAZ0+pQlqVjROdJTjQAeQ4M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.77 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f77.google.com with SMTP id 006d021491bc7-68826165bc9so641861eaf.0 for ; Fri, 17 Apr 2026 06:37:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776433040; x=1777037840; h=content-transfer-encoding:to:from:subject:message-id:in-reply-to :date:mime-version:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=U3+/j26jyD0jCPDtwRMMkl5wbWrWC5bhBKJAQGo+hH0=; b=gkSY+jbixOAyhHesvCCcIeceghA77emfCSh6ebebGllF+wSVnrilJSBhXD5bLRmKSL WWB0EH1Innzwn29V+OjffA5QwMjchnOhwvafbRC7+gW5bngVHd9WpUSPLHmvwWzKBGlk KHfTUdcIvVDZaX+NAHKDFZNssGixx612HgMIBuCpaQZsfxB9SnJ1j6gdqlhxI1MrQ/iF VO/hu+u2rqrKHy3XBD3yuJ8jOfyYwUfjNEe8NpXqkwjWhNJfqZUUl3pr21gPzVA5ziyh mJjQjR3eWL8BZ/jcnPI08rAoH17OceTUk56zBSHJxwGh3UfWaIb7bSq4ZG5uWHlaaczX RxLg== X-Gm-Message-State: AOJu0YyPEbQtYkIOqbHmxlLP94j+xwUngk+0BcQdkGcCwgUP9799mrYf jwiEdkVxJ7y5CA1wsPilaMS77rTVYI30l6NAG5x2YeGEdmP0TsvP13iMl/3NmTxp96JEW8nq07s UWtZJ8lFJVznJJTlYlLbvCdKiaURMOyUxnJ6OZ5Wt0R+V6ykCjtSqpsIWWwHfIg== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:1c8f:b0:68c:1689:697d with SMTP id 006d021491bc7-69462f108edmr1406960eaf.42.1776433039893; Fri, 17 Apr 2026 06:37:19 -0700 (PDT) Date: Fri, 17 Apr 2026 06:37:19 -0700 In-Reply-To: <69d678c4.050a0220.3030df.000a.GAE@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69e2378f.a00a0220.1bd0ca.0003.GAE@google.com> Subject: Forwarded: Re: [syzbot] [net?] memory leak in xfrm_policy_construct From: syzbot To: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org. *** Subject: Re: [syzbot] [net?] memory leak in xfrm_policy_construct Author: nogikh@google.com Hi Helen, Thanks for looking into the issue! Nit: it's better to directly Cc original syzbot emails (syzbot+901d48e0b95aed4a2548@syzkaller.appspotmail.com in this case) when sending commands to it, otherwise it may not recognize the bug. #syz fix: xfrm: fix refcount leak in xfrm_migrate_policy_find --=20 Aleksandr On Fri, Apr 17, 2026 at 3:32=E2=80=AFPM Helen Koike wrot= e: > > Hey all, > > I just noticed I couldn't reproduce on 7.0 upstream/master (3cd8b194bf34)= , and from a bisect I found that commit 83317cce60a0 "xfrm: fix refcount le= ak in xfrm_migrate_policy_find" fixes this issue. Which is clear by the com= mit message and I also reverted it on upstream/master and validated it repr= oduces. So I'm marking it as fixed: > > #syz fix: "xfrm: fix refcount leak in xfrm_migrate_policy_find" > > Em s=C3=A1bado, 11 de abril de 2026 =C3=A0s 22:27:03 UTC-3, syzbot escrev= eu: >> >> Hello, >> >> syzbot has tested the proposed patch and the reproducer did not trigger = any issue: >> >> Reported-by: syzbot+901d48...@syzkaller.appspotmail.com >> Tested-by: syzbot+901d48...@syzkaller.appspotmail.com >> >> Tested on: >> >> commit: f5459048 Merge tag 'i2c-for-7.0-final' of git://git.ke.. >> git tree: upstream >> console output: https://syzkaller.appspot.com/x/log.txt?x=3D12b8f3025800= 00 >> kernel config: https://syzkaller.appspot.com/x/.config?x=3De2bba615ee79f= aa5 >> dashboard link: https://syzkaller.appspot.com/bug?extid=3D901d48e0b95aed= 4a2548 >> compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian= ) 2.44 >> patch: https://syzkaller.appspot.com/x/patch.diff?x=3D14e2c74e580000 >> >> Note: testing is done by a robot and is best-effort only. > > -- > You received this message because you are subscribed to the Google Groups= "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an= email to syzkaller-bugs+unsubscribe@googlegroups.com. > To view this discussion visit https://groups.google.com/d/msgid/syzkaller= -bugs/8b891373-c70d-4fa9-b8b1-8c1fa06e0756n%40googlegroups.com.