linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+fcc629d1a1ae8d3fe8a5@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	tadeusz.struk@linaro.org, tytso@mit.edu
Subject: Re: [syzbot] kernel BUG in ext4_ind_remove_space
Date: Tue, 15 Mar 2022 13:22:05 -0700	[thread overview]
Message-ID: <000000000000f422ca05da478cae@google.com> (raw)
In-Reply-To: <a30ec1e7-564f-665b-7c20-54dad6124418@linaro.org>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to apply patch:
checking file fs/ext4/inode.c
patch: **** unexpected end of file in patch



Tested on:

commit:         56e337f2 Revert "gpio: Revert regression in sysfs-gpio..
git tree:       upstream
dashboard link: https://syzkaller.appspot.com/bug?extid=fcc629d1a1ae8d3fe8a5
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=14bf8361700000


  reply	other threads:[~2022-03-15 20:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14  1:58 [syzbot] kernel BUG in ext4_ind_remove_space syzbot
2022-03-15 15:14 ` syzbot
2022-03-15 19:21   ` Tadeusz Struk
2022-03-15 20:22     ` syzbot [this message]
2022-03-15 21:38   ` [PATCH v2] ext4: check if offset+length is within valid fallocate Tadeusz Struk
2022-03-15 21:48     ` [syzbot] kernel BUG in ext4_ind_remove_space syzbot
2022-04-28 14:02     ` [PATCH v2] ext4: check if offset+length is within valid fallocate Jan Kara
2022-05-04 14:08       ` Tadeusz Struk
2022-05-09 16:41 ` [syzbot] kernel BUG in ext4_ind_remove_space 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=000000000000f422ca05da478cae@google.com \
    --to=syzbot+fcc629d1a1ae8d3fe8a5@syzkaller.appspotmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tadeusz.struk@linaro.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).