From: syzbot <syzbot+c5b339d16ffa61fd512d@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [ntfs3?] WARNING in indx_insert_into_buffer
Date: Thu, 23 Nov 2023 17:12:21 -0800 [thread overview]
Message-ID: <000000000000ea17f4060adba4d9@google.com> (raw)
In-Reply-To: <000000000000fb2f84060ad4da7f@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [ntfs3?] WARNING in indx_insert_into_buffer
Author: lizhi.xu@windriver.com
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 037266a5f723
diff --git a/fs/ntfs3/index.c b/fs/ntfs3/index.c
index cf92b2433f7a..e6b59cb87769 100644
--- a/fs/ntfs3/index.c
+++ b/fs/ntfs3/index.c
@@ -1905,6 +1905,8 @@ indx_insert_into_buffer(struct ntfs_index *indx, struct ntfs_inode *ni,
}
if (err) {
+ if (err == -ENOMEM || err == -EINVAL)
+ goto out;
/*
* Undo critical operations.
*/
next prev parent reply other threads:[~2023-11-24 1:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 17:06 [syzbot] [ntfs3?] WARNING in indx_insert_into_buffer syzbot
2023-11-24 1:12 ` syzbot [this message]
2023-11-24 2:07 ` syzbot
2023-11-24 2:51 ` syzbot
2023-11-24 11:21 ` syzbot
2023-11-24 13:13 ` syzbot
2023-11-24 14:08 ` syzbot
2023-11-25 2:46 ` syzbot
2023-11-25 3:35 ` syzbot
2023-11-25 8:12 ` syzbot
2023-11-25 10:35 ` syzbot
2023-11-25 12:42 ` syzbot
[not found] <20231124011216.3062608-1-lizhi.xu@windriver.com>
2023-11-24 1:33 ` syzbot
[not found] <20231124020744.3444746-1-lizhi.xu@windriver.com>
2023-11-24 2:23 ` syzbot
[not found] <20231124025100.2028923-1-lizhi.xu@windriver.com>
2023-11-24 3:06 ` syzbot
[not found] <tencent_75989238DDDB5DCA9922CFBF8DD225A38D07@qq.com>
2023-11-24 12:25 ` syzbot
[not found] <tencent_37ADAED3EECFCC9567ED06EA52C2C6488906@qq.com>
2023-11-24 13:51 ` syzbot
[not found] <tencent_47C9842EF3AED1CC8927C046F412C5066506@qq.com>
2023-11-24 14:30 ` syzbot
[not found] <tencent_056CDC97A4E816ED46CDD879F66C402C450A@qq.com>
2023-11-25 2:58 ` syzbot
[not found] <tencent_C74A927585770766383DEF373C96C8360E09@qq.com>
2023-11-25 3:56 ` syzbot
[not found] <tencent_0A75760B67463C59368097E436204B587409@qq.com>
2023-11-25 8:31 ` syzbot
[not found] <tencent_BFC9C6EF52D0C64F09BAAEE06ECACC82A706@qq.com>
2023-11-25 10:45 ` syzbot
[not found] <tencent_18F764177706CB137F63662968E3A6645A05@qq.com>
2023-11-25 12:58 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2023-11-29 11:06 [syzbot] [net?] general protection fault in page_pool_unlist syzbot
2023-11-30 6:25 ` [syzbot] [ntfs3?] WARNING in indx_insert_into_buffer 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=000000000000ea17f4060adba4d9@google.com \
--to=syzbot+c5b339d16ffa61fd512d@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.