From: Greg KH <greg@kroah.com>
To: Machiry Aravind Kumar <makrvcs@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Help filing bugs from crash reports and repro files.
Date: Sun, 21 Mar 2021 21:53:19 +0100 [thread overview]
Message-ID: <YFeyP6tpheZg9P2c@kroah.com> (raw)
In-Reply-To: <CAAwk1nK3ouYjMuBE8CBXMSAb3aCH9hNK-jFfVfQe+pRnhrzcNA@mail.gmail.com>
On Wed, Mar 17, 2021 at 12:36:58AM -0400, Machiry Aravind Kumar wrote:
> Hello all,
>
> We have modified the syzkaller a bit to be more effective at finding
> kernel bugs.
> Attached are the crashes along with a reproducer .c file.
>
> Any help in figuring out the underlying bug and submitting a patch is
> greatly appreciated!
Please submit the crash report to the subsystem where the crash is,
compressed files do not work for responding in emails.
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-03-21 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 4:36 Help filing bugs from crash reports and repro files Machiry Aravind Kumar
2021-03-21 20:53 ` Greg KH [this message]
2021-03-21 20:56 ` Greg KH
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=YFeyP6tpheZg9P2c@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=makrvcs@gmail.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).