From: syzbot <syzbot+df61b36319e045c00a08@syzkaller.appspotmail.com>
To: glider@google.com, linux-kernel@vger.kernel.org,
pchelkin@ispras.ru, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] KMSAN: uninit-value in ath9k_hw_init
Date: Wed, 15 Mar 2023 12:45:27 -0700 [thread overview]
Message-ID: <00000000000000dabd05f6f59668@google.com> (raw)
In-Reply-To: <20230315193521.jcox7j3is24gk6mj@fpc>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file drivers/net/wireless/ath/ath9k/wmi.c
Hunk #1 FAILED at 200.
Hunk #2 succeeded at 234 (offset -8 lines).
Hunk #3 succeeded at 291 (offset -8 lines).
Hunk #4 succeeded at 302 (offset -8 lines).
Hunk #5 succeeded at 347 (offset -8 lines).
1 out of 5 hunks FAILED
Tested on:
commit: 34add094 kmsan: add test_stackdepot_roundtrip
git tree: https://github.com/google/kmsan.git master
dashboard link: https://syzkaller.appspot.com/bug?extid=df61b36319e045c00a08
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=124d82a4c80000
next prev parent reply other threads:[~2023-03-15 19:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 19:35 [syzbot] [wireless?] KMSAN: uninit-value in ath9k_hw_init Fedor Pchelkin
2023-03-15 19:45 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 13:47 Fedor Pchelkin
2023-03-15 14:12 ` syzbot
2023-03-13 20:47 Fedor Pchelkin
2023-03-13 21:05 ` syzbot
2023-03-13 17:41 Fedor Pchelkin
2023-03-13 18:04 ` syzbot
2023-03-13 17:05 Fedor Pchelkin
2023-03-13 17:35 ` syzbot
2023-03-13 14:36 Fedor Pchelkin
2023-03-13 15:46 ` syzbot
2023-03-13 11:02 Fedor Pchelkin
2023-03-13 11:22 ` syzbot
2023-03-12 20:21 Fedor Pchelkin
2023-03-12 20:41 ` [syzbot] [wireless?] KMSAN: uninit-value in ath9k_hw_init syzbot
2023-03-06 7:22 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=00000000000000dabd05f6f59668@google.com \
--to=syzbot+df61b36319e045c00a08@syzkaller.appspotmail.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pchelkin@ispras.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.