linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Sanan Hasanov <Sanan.Hasanov@ucf.edu>,
	"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"syzkaller@googlegroups.com" <syzkaller@googlegroups.com>,
	"contact@pgazz.com" <contact@pgazz.com>
Subject: Re: general protection fault in ext4_update_overhead
Date: Tue, 12 Sep 2023 16:50:47 -0700	[thread overview]
Message-ID: <20230912235047.GA11463@frogsfrogsfrogs> (raw)
In-Reply-To: <20230912234112.GA1294595@mit.edu>

On Tue, Sep 12, 2023 at 07:41:12PM -0400, Theodore Ts'o wrote:
> On Tue, Sep 12, 2023 at 11:02:35PM +0000, Sanan Hasanov wrote:
> > Good day, dear maintainers,
> > 
> > We found a bug using a modified kernel configuration file used by syzbot.
> > 
> > We enhanced the coverage of the configuration file using our tool, klocalizer.
> > 
> > Kernel Branch: 6.3.0-next-20230426

Also this was from            ^^^^^^^^ four months ago.

Why are you wasting Ted and everyone else's time with this?

--D

> > Kernel Config: https://drive.google.com/file/d/1xpe7qMUUYvHQFzqZGUzcco9jF97EwTqQ/view?usp=sharing
> > Reproducer: https://drive.google.com/file/d/1Q8ix6EiWrzx0bWLyoGTHP721KE4Ei3qf/view?usp=sharing
> 
> The reproducer is a zero-length file.  So I can do nothing with this
> report.
> 
> Note that the official syzbot instance will do automatic bisection,
> and will allow us to test patches.  The official syzbot instance also
> processes the console output so that the stack trace has line numbers
> and clickable links to the kernel sources.
> 
> This report is **much** less useful than the syzbot report, so please
> don't be surprised if people treat this at a significantly lower
> priority.  (Even if the reproducer wasn't a zero length file.  :-P  )
> 
> 	   	    		   	  - Ted

      reply	other threads:[~2023-09-12 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 23:02 general protection fault in ext4_update_overhead Sanan Hasanov
2023-09-12 23:41 ` Theodore Ts'o
2023-09-12 23:50   ` Darrick J. Wong [this message]

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=20230912235047.GA11463@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=Sanan.Hasanov@ucf.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=contact@pgazz.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller@googlegroups.com \
    --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).