From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 26C98C6FA9D for ; Wed, 1 Mar 2023 17:04:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230015AbjCAREV (ORCPT ); Wed, 1 Mar 2023 12:04:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35338 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229989AbjCAREU (ORCPT ); Wed, 1 Mar 2023 12:04:20 -0500 Received: from mail-io1-f71.google.com (mail-io1-f71.google.com [209.85.166.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C791E43924 for ; Wed, 1 Mar 2023 09:04:06 -0800 (PST) Received: by mail-io1-f71.google.com with SMTP id s1-20020a6bd301000000b0073e7646594aso9072737iob.8 for ; Wed, 01 Mar 2023 09:04:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=4ijtyYwUSpPiADlS8jXaq8RNP7rAhwQrJbgxXtqNnsk=; b=Eoy1C6iMLFJdb4paFiW43kHa7yCOHIiioZzBarzcIZytkSY+chpSyFH9kU6BEhwgCi LMvSlf9hubdaRzTZFEKvjhtbRJ0w1Rr5pkM+w5Zjj3ESx+6VSGjY0MmpHrQpQQiPJSqJ f8kzC4VX8KmxnFaxMR+wWqwduWZj1h7sgD8gXyN8BnPj/MUYnX41NC9d7eHL35KZvkTK jaQtw6K8w3ausbHZE4rzYh4AhAAb78af4kQ+SEdG12ydbmsE5rRGt/TNOplpu/OT8iXo IX8Hub6H5NZTi2GxZiUz214WuZ02tlTYWiwBnGl2kefG5MdMUMpbsHCrRum5z5JP9xRq k8ow== X-Gm-Message-State: AO0yUKWaJ0El4AGzBPLv53Xe1d4B7tYdYwape312QtFDc8zBs3GFLO1v aB4IAL52tu6i1kyZYje88KRkMeULQgiizJRrU+J6jYJCOg6t X-Google-Smtp-Source: AK7set8uFRynAEITgWsfrGesrBup2CAk3VxbpWdX/bYU859iY/Hj9DUIPdja/medu71lSLKEl+EqARAhgw2v71t/elag0Fpb4znZ MIME-Version: 1.0 X-Received: by 2002:a02:3312:0:b0:3c4:dda2:da6e with SMTP id c18-20020a023312000000b003c4dda2da6emr3316494jae.4.1677690246030; Wed, 01 Mar 2023 09:04:06 -0800 (PST) Date: Wed, 01 Mar 2023 09:04:06 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000286e1a05f5d9b3c6@google.com> Subject: [syzbot] [ext4?] memory leak in ext4_expand_extra_isize_ea From: syzbot To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, tytso@mit.edu Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: c0927a7a5391 Merge tag 'xfs-6.3-merge-4' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10d973a8c80000 kernel config: https://syzkaller.appspot.com/x/.config?x=f5733ca1757172ad dashboard link: https://syzkaller.appspot.com/bug?extid=0d042627c4f2ad332195 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16598c22c80000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12376874c80000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/a5732f39d793/disk-c0927a7a.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/a0b9fb85e380/vmlinux-c0927a7a.xz kernel image: https://storage.googleapis.com/syzbot-assets/0f4253a65ff3/bzImage-c0927a7a.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/2162c5bd66e2/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+0d042627c4f2ad332195@syzkaller.appspotmail.com BUG: memory leak unreferenced object 0xffff88810658dc00 (size 1024): comm "syz-executor463", pid 5080, jiffies 4294961132 (age 13.510s) hex dump (first 32 bytes): 00 fb 8e 00 00 cf e8 9e ac aa 80 5a e1 26 a9 9c ...........Z.&.. 71 e3 ea 67 33 7f 9a ef ca d1 17 51 5c 7f 0e 4b q..g3......Q\..K backtrace: [] __do_kmalloc_node mm/slab_common.c:966 [inline] [] __kmalloc_node+0x4d/0x120 mm/slab_common.c:974 [] kmalloc_node include/linux/slab.h:610 [inline] [] kvmalloc_node+0xa2/0x180 mm/util.c:603 [] kvmalloc include/linux/slab.h:737 [inline] [] ext4_xattr_move_to_block fs/ext4/xattr.c:2635 [inline] [] ext4_xattr_make_inode_space fs/ext4/xattr.c:2743 [inline] [] ext4_expand_extra_isize_ea+0x786/0xb80 fs/ext4/xattr.c:2835 [] __ext4_expand_extra_isize+0x18b/0x200 fs/ext4/inode.c:5955 [] ext4_try_to_expand_extra_isize fs/ext4/inode.c:5998 [inline] [] __ext4_mark_inode_dirty+0x245/0x370 fs/ext4/inode.c:6076 [] ext4_set_acl+0x21e/0x340 fs/ext4/acl.c:263 [] set_posix_acl+0x112/0x150 fs/posix_acl.c:956 [] vfs_set_acl+0x2b2/0x4a0 fs/posix_acl.c:1098 [] do_set_acl+0x90/0x140 fs/posix_acl.c:1247 [] do_setxattr+0x73/0xf0 fs/xattr.c:606 [] setxattr+0xbd/0xe0 fs/xattr.c:632 [] path_setxattr+0x118/0x130 fs/xattr.c:651 [] __do_sys_lsetxattr fs/xattr.c:674 [inline] [] __se_sys_lsetxattr fs/xattr.c:670 [inline] [] __x64_sys_lsetxattr+0x29/0x30 fs/xattr.c:670 [] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 [] entry_SYSCALL_64_after_hwframe+0x63/0xcd --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches