linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Shreeya Patel <shreeya.patel@collabora.com>
Cc: "Thorsten Leemhuis" <regressions@leemhuis.info>,
	"Andres Freund" <andres@anarazel.de>,
	linux-ext4@vger.kernel.org,
	"Ricardo Cañuelo" <ricardo.canuelo@collabora.com>,
	"gustavo.padovan@collabora.com" <gustavo.padovan@collabora.com>,
	groeck@google.com, zsm@google.com, garrick@google.com,
	"Linux regressions mailing list" <regressions@lists.linux.dev>
Subject: Re: [syzbot] INFO: task hung in ext4_fallocate
Date: Fri, 13 Oct 2023 21:54:53 -0400	[thread overview]
Message-ID: <20231014015453.GE255452@mit.edu> (raw)
In-Reply-To: <e6277feb-e444-4d47-8376-fa2909fbac96@collabora.com>

On Fri, Oct 13, 2023 at 02:28:52AM +0530, Shreeya Patel wrote:
> 
> Just to clarify, this issue is still seen on upstream 5.10 and earlier
> kernels.
> I can confirm that we did not see this issue being reproduced on mainline
> kernel using #sys test feature.

So I'm confused.  In the original post on this thread[1], it was stated:

> When I tried to reproduce this issue on mainline linux kernel using the 
> reproducer provided by syzbot, I see an endless loop of following errors :-

and

> #regzbot introduced: v6.6-rc1..

[1] https://lore.kernel.org/all/d89989ef-e53b-050e-2916-a4f06433798b@collabora.com/

... and now you're sayingg this *wasn't* reproduced upstream?  And of
course, because this was a private syzbot instance, there was syzbot
dashboard given, and the reproducer had the serial number filed off
(there is a URL in the comments at the beginning of the reproducer for
a *reason*), so *I* couldn't run "#syz test".

Huh?

Reading between the lines, it looks like the only similarity between
what was happening in the 5.10 kernel and the mainline kernel was that
it did not *hang* the kernel, but it was generating a stream of
EXT4-fs error messages.  Well, if you take a deliberately corrupted
kernel, and mount it with errors=continue, and then keep pounding it
with lots of file system operations, of *course* it will continually
spew ext4 errors message.  That is "Working As Intended" by
*definition*.

And this is why I maintain that irresponsible use of syzbot is
effectively a denial of service attack on upstream maintainers.

At this point, just as upstream policy is that debugging ancient LTS
kernels is not something upstream maintainers to do (and attempting to
trick them to debug it by claiming it is found in mainline is *really*
uncool), if there are bugs that are reported using private syzbot
instances, or where there isn't a URL to a public syzbot dashboard,
they should be treated as P4 priority or worse....

	      	     		       	  - Ted


  reply	other threads:[~2023-10-14  1:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 14:43 [syzbot] INFO: task hung in ext4_fallocate Shreeya Patel
2023-09-18 22:07 ` Theodore Ts'o
2023-10-03 14:11   ` Andres Freund
2023-10-03 23:25     ` Theodore Ts'o
2023-10-04  0:42       ` Andres Freund
2023-10-05  9:04         ` Shreeya Patel
2023-10-10  9:21           ` Thorsten Leemhuis
2023-10-10 16:25             ` Andres Freund
2023-10-12 20:58             ` Shreeya Patel
2023-10-14  1:54               ` Theodore Ts'o [this message]
2023-10-17 14:58                 ` Shreeya Patel

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=20231014015453.GE255452@mit.edu \
    --to=tytso@mit.edu \
    --cc=andres@anarazel.de \
    --cc=garrick@google.com \
    --cc=groeck@google.com \
    --cc=gustavo.padovan@collabora.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=ricardo.canuelo@collabora.com \
    --cc=shreeya.patel@collabora.com \
    --cc=zsm@google.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;
as well as URLs for NNTP newsgroup(s).