From: Edward Adam Davis <eadavis@qq.com>
To: syzbot+d2125fcb6aa8c4276fd2@syzkaller.appspotmail.com
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] general protection fault in iter_file_splice_write
Date: Wed, 22 May 2024 20:49:03 +0800 [thread overview]
Message-ID: <tencent_7BF20C9927C0C6D292CCC64BC994EEF92E06@qq.com> (raw)
In-Reply-To: <0000000000002fd2de0618de2e65@google.com>
please test null ptr in iter_file_splice_write
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 33e02dc69afb
diff --git a/fs/splice.c b/fs/splice.c
index 60aed8de21f8..8ec408c40755 100644
--- a/fs/splice.c
+++ b/fs/splice.c
@@ -715,6 +715,7 @@ iter_file_splice_write(struct pipe_inode_info *pipe, struct file *out,
/* build the vector */
left = sd.total_len;
+ printk("total len: %lu, %s\n", left, __func__);
for (n = 0; !pipe_empty(head, tail) && left && n < nbufs; tail++) {
struct pipe_buffer *buf = &pipe->bufs[tail & mask];
size_t this_len = buf->len;
@@ -751,9 +752,16 @@ iter_file_splice_write(struct pipe_inode_info *pipe, struct file *out,
/* dismiss the fully eaten buffers, adjust the partial one */
tail = pipe->tail;
- while (ret) {
+ printk("ret: %ld, nbufs: %d, %s\n", ret, nbufs, __func__);
+ n = 0;
+ while (ret > 0 && n < nbufs) {
struct pipe_buffer *buf = &pipe->bufs[tail & mask];
- if (ret >= buf->len) {
+ if (!buf->len) {
+ tail++;
+ continue;
+ }
+ printk("buf len: %lu, %s\n", buf->len, __func__);
+ if (ret >= (ssize_t)buf->len) {
ret -= buf->len;
buf->len = 0;
pipe_buf_release(pipe, buf);
@@ -766,6 +774,7 @@ iter_file_splice_write(struct pipe_inode_info *pipe, struct file *out,
buf->len -= ret;
ret = 0;
}
+ n++;
}
}
done:
next prev parent reply other threads:[~2024-05-22 12:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 8:06 syzbot
2024-05-22 5:21 ` Edward Adam Davis
2024-05-22 5:45 ` syzbot
2024-05-22 10:37 ` Edward Adam Davis
2024-05-22 10:57 ` syzbot
2024-05-22 11:30 ` Edward Adam Davis
2024-05-22 11:56 ` syzbot
2024-05-22 12:49 ` Edward Adam Davis [this message]
2024-05-22 13:13 ` syzbot
2024-05-22 13:29 ` Edward Adam Davis
2024-05-22 13:54 ` syzbot
2024-05-22 14:05 ` Edward Adam Davis
2024-05-22 14:30 ` syzbot
2024-05-23 8:33 ` [syzbot] " syzbot
2024-05-23 9:23 ` syzbot
2024-05-23 12:33 ` Edward Adam Davis
2024-05-23 12:58 ` syzbot
2024-05-23 14:13 ` Edward Adam Davis
2024-05-23 14:37 ` syzbot
2024-05-24 0:52 ` [syzbot] " syzbot
2024-05-24 1:30 ` syzbot
2024-05-24 2:07 ` syzbot
2024-05-24 3:51 ` syzbot
2024-05-24 5:35 ` [PATCH] netfs: if extracting pages from user iterator fails return 0 Lizhi Xu
2024-08-11 22:43 ` [syzbot] [fs?] general protection fault in iter_file_splice_write syzbot
2025-09-23 19:59 ` syzbot
2025-09-25 12:47 ` David Howells
[not found] <20240523083332.761304-1-lizhi.xu@windriver.com>
2024-05-23 8:58 ` syzbot
[not found] <20240523092352.1279292-1-lizhi.xu@windriver.com>
2024-05-23 9:36 ` syzbot
[not found] <20240524005225.2834298-1-lizhi.xu@windriver.com>
2024-05-24 1:15 ` syzbot
[not found] <20240524012956.3069071-1-lizhi.xu@windriver.com>
2024-05-24 1:51 ` syzbot
[not found] <20240524020717.1126466-1-lizhi.xu@windriver.com>
2024-05-24 2:31 ` syzbot
[not found] <20240524035136.1561347-1-lizhi.xu@windriver.com>
2024-05-24 4:16 ` 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=tencent_7BF20C9927C0C6D292CCC64BC994EEF92E06@qq.com \
--to=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+d2125fcb6aa8c4276fd2@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®