From: syzbot <syzbot+11af34d3c0711f233fd4@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, norbert.kaminski@infogain.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] KASAN: use-after-free Read in __ext4_check_dir_entry (2)
Date: Wed, 26 Jun 2024 01:10:03 -0700 [thread overview]
Message-ID: <0000000000009de4dc061bc68ac3@google.com> (raw)
In-Reply-To: <20240626080337.32736-1-norbert.kaminski@infogain.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
scripts/extract-cert.c:46:9: warning: 'ERR_get_error_line' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
scripts/extract-cert.c:59:9: warning: 'ERR_get_error_line' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
scripts/sign-file.c:89:9: warning: 'ERR_get_error_line' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
scripts/sign-file.c:102:9: warning: 'ERR_get_error_line' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
orc_dump.c:106:9: error: 'elf_getshnum' is deprecated [-Werror=deprecated-declarations]
orc_dump.c:111:9: error: 'elf_getshstrndx' is deprecated [-Werror=deprecated-declarations]
elf.c:135:9: error: 'elf_getshnum' is deprecated [-Werror=deprecated-declarations]
elf.c:140:9: error: 'elf_getshstrndx' is deprecated [-Werror=deprecated-declarations]
subcmd-util.h:56:23: error: pointer may be used after 'realloc' [-Werror=use-after-free]
subcmd-util.h:58:31: error: pointer may be used after 'realloc' [-Werror=use-after-free]
Tested on:
commit: e40ff213 ext4: force revalidation of directory pointer..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=9d7ea7de0cb32587
dashboard link: https://syzkaller.appspot.com/bug?extid=11af34d3c0711f233fd4
compiler: Debian clang version 15.0.6
Note: no patches were applied.
next parent reply other threads:[~2024-06-26 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240626080337.32736-1-norbert.kaminski@infogain.com>
2024-06-26 8:10 ` syzbot [this message]
[not found] <20240626074013.30611-1-norbert.kaminski@3mdeb.com>
2024-06-26 7:55 ` [syzbot] [ext4?] KASAN: use-after-free Read in __ext4_check_dir_entry (2) syzbot
[not found] <20240516183454.GA287325@mit.edu>
2024-05-16 19:25 ` syzbot
[not found] <20240515230145.GB202157@mit.edu>
2024-05-16 0:01 ` syzbot
2024-05-14 14:09 syzbot
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=0000000000009de4dc061bc68ac3@google.com \
--to=syzbot+11af34d3c0711f233fd4@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=norbert.kaminski@infogain.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