t will go away by itself.
> it didn't, so I am posting
> a bug report.
>
> The ./nci_dev seems to be stuck in several processes waiting on each other. I
> was able to produce
> stacktraces. I am unable to tell if it is testsuite bug or a problem in
> underlying syscall
> After several tests, I found that the same PoC can cause multiple
> different crashes for some unknown reason. Thus, I suspect that the
> bug is capable of performing unintended memory writing without being
> caught by KASAN.
> I tested the PoC on the latest kernel, Linux 6.11
After several tests, I found that the same PoC can cause multiple
different crashes for some unknown reason. Thus, I suspect that the
bug is capable of performing unintended memory writing without being
caught by KASAN.
I tested the PoC on the latest kernel, Linux 6.11 rc7 and it can still
cause
your "reproducer" on 6.11.0-rc2. I see some panics and they are
> different. For example below one triggers: BUG: kernel NULL pointer
> dereference, address: 0010
>
>
> Linux pc640 6.11.0-rc2-00037-g6b376d473b12 #3833 SMP PREEMPT_DYNAMIC Thu Sep
> 12 15:42:
> > >
> > > Here is the config file:
> > > https://gist.github.com/TomAPU/64f5db0fe976a3e94a6dd2b621887cdd
> > >
I tested your "reproducer" on 6.11.0-rc2. I see some panics and they are
different. For example below one triggers: BUG: kernel NULL p
Here is to set up the reproducing environment:
https://github.com/TomAPU/Linux610BugReort
We tested it, and it can reproduce.
On Wed, Sep 4, 2024 at 10:52 AM Uladzislau Rezki wrote:
>
> Hello!
>
> >
> > Here is the config file:
> > https://gist.github.com/TomAPU/64f5db0fe976a3e94a6dd2b621887cdd
>
Hello!
>
> Here is the config file:
> https://gist.github.com/TomAPU/64f5db0fe976a3e94a6dd2b621887cdd
>
Thank you. I was not able to boot my box using your config file. But i
enabled all needed configs in to run your reproduce so it does not
complain on below warnings:
urezki@pc638:~$ sudo ./a.
On Wed, 21 Aug 2024 11:50:00 -0400
Steven Rostedt wrote:
> On Wed, 21 Aug 2024 16:42:07 +0100
> Mark Rutland wrote:
>
> > FWIW, that was in samples/ftrace/ftrace-ops.c, where tracee_relevant() and
> > tracee_irrelevant() have the barrier():
> >
> > | /*
> > | * Marked as noinline to ensure th
On Wed, 21 Aug 2024 16:42:07 +0100
Mark Rutland wrote:
> FWIW, that was in samples/ftrace/ftrace-ops.c, where tracee_relevant() and
> tracee_irrelevant() have the barrier():
>
> | /*
> | * Marked as noinline to ensure that an out-of-line traceable copy is
> | * generated by the compiler.
> |
On Wed, Aug 21, 2024 at 04:32:46PM +0100, Mark Rutland wrote:
> On Wed, Aug 21, 2024 at 07:05:39AM +0900, Masami Hiramatsu wrote:
> > On Tue, 20 Aug 2024 08:10:42 -0700
> > Sami Tolvanen wrote:
> >
> > > On Tue, Aug 20, 2024 at 3:48 AM Mark Rutland wrote:
> > > >
> > > > On Tue, Aug 20, 2024 at
On Wed, Aug 21, 2024 at 07:05:39AM +0900, Masami Hiramatsu wrote:
> On Tue, 20 Aug 2024 08:10:42 -0700
> Sami Tolvanen wrote:
>
> > On Tue, Aug 20, 2024 at 3:48 AM Mark Rutland wrote:
> > >
> > > On Tue, Aug 20, 2024 at 10:03:30AM +0900, Masami Hiramatsu wrote:
> > > > On Mon, 19 Aug 2024 12:02:
On Tue, Aug 20, 2024 at 5:21 PM Masami Hiramatsu wrote:
>
> On Wed, 21 Aug 2024 08:43:51 +0900
> Masami Hiramatsu (Google) wrote:
>
> > On Tue, 20 Aug 2024 18:11:09 -0400
> > Steven Rostedt wrote:
> >
> > > On Wed, 21 Aug 2024 07:05:39 +0900
> > > Masami Hiramatsu (Google) wrote:
> > >
> > >
>
On Wed, 21 Aug 2024 08:43:51 +0900
Masami Hiramatsu (Google) wrote:
> On Tue, 20 Aug 2024 18:11:09 -0400
> Steven Rostedt wrote:
>
> > On Wed, 21 Aug 2024 07:05:39 +0900
> > Masami Hiramatsu (Google) wrote:
> >
> >
> > > Does the noinline attribute prevent embedding callsite too? I mean
> >
does
> > not change, the test still fails.
>
> OK, now that sounds like a bug in LTO itself.
Hmm, I think __used just preserve the function exists as a function. But the
callsite can be optimized. This mean the __used function code is duplicated,
and embedded one copy in the callsite,
On Wed, 21 Aug 2024 08:43:51 +0900
Masami Hiramatsu (Google) wrote:
> > Can you add the __used and see if it fixes it?
>
> Adding __used to DYN_FTRACE_TEST_NAME() and DYN_FTRACE_TEST_NAME2() does
> not change, the test still fails.
OK, now that sounds like a bug in LTO itself.
-- Steve
On Tue, 20 Aug 2024 18:11:09 -0400
Steven Rostedt wrote:
> On Wed, 21 Aug 2024 07:05:39 +0900
> Masami Hiramatsu (Google) wrote:
>
>
> > Does the noinline attribute prevent embedding callsite too? I mean
> >
> > extern callee()
> >
> > noinline callee()
> > {
> > ...
> > }
> >
> > caller()
On Wed, 21 Aug 2024 07:05:39 +0900
Masami Hiramatsu (Google) wrote:
> Does the noinline attribute prevent embedding callsite too? I mean
>
> extern callee()
>
> noinline callee()
> {
> ...
> }
>
> caller()
> {
> callee() // (*)
> }
>
> In this case, does noinline prevent LTO to embed t
On Tue, 20 Aug 2024 08:10:42 -0700
Sami Tolvanen wrote:
> On Tue, Aug 20, 2024 at 3:48 AM Mark Rutland wrote:
> >
> > On Tue, Aug 20, 2024 at 10:03:30AM +0900, Masami Hiramatsu wrote:
> > > On Mon, 19 Aug 2024 12:02:44 -0400
> > > Steven Rostedt wrote:
> > >
> > > > On Tue, 20 Aug 2024 00:56:49
On Tue, 20 Aug 2024 08:10:42 -0700
Sami Tolvanen wrote:
> On Tue, Aug 20, 2024 at 3:48 AM Mark Rutland wrote:
> >
> > On Tue, Aug 20, 2024 at 10:03:30AM +0900, Masami Hiramatsu wrote:
> > > On Mon, 19 Aug 2024 12:02:44 -0400
> > > Steven Rostedt wrote:
> > >
> > > > On Tue, 20 Aug 2024 00:5
On Tue, Aug 20, 2024 at 3:48 AM Mark Rutland wrote:
>
> On Tue, Aug 20, 2024 at 10:03:30AM +0900, Masami Hiramatsu wrote:
> > On Mon, 19 Aug 2024 12:02:44 -0400
> > Steven Rostedt wrote:
> >
> > > On Tue, 20 Aug 2024 00:56:49 +0900
> > > Masami Hiramatsu (Google) wrote:
> > > >
> > > > >
> > > >
On Tue, 20 Aug 2024 11:48:07 +0100
Mark Rutland wrote:
> > I found the target function already has "noinline". I tried to add noinline
> > to the testing function (callsite), but it also did not work.
> > I think "noinline" is for the compiler, but LTO is done by the linker.
>
> If LTO is brea
On Tue, Aug 20, 2024 at 10:03:30AM +0900, Masami Hiramatsu wrote:
> On Mon, 19 Aug 2024 12:02:44 -0400
> Steven Rostedt wrote:
>
> > On Tue, 20 Aug 2024 00:56:49 +0900
> > Masami Hiramatsu (Google) wrote:
> > >
> > > >
> > > > We may need to add "noinline" or something to make sure those funct
On Mon, 19 Aug 2024 12:02:44 -0400
Steven Rostedt wrote:
> On Tue, 20 Aug 2024 00:56:49 +0900
> Masami Hiramatsu (Google) wrote:
> >
> > >
> > > We may need to add "noinline" or something to make sure those functions
> > > don't get inlined for LTO.
> >
> > Yeah, we need such option at leas
On Mon, 19 Aug 2024 12:02:44 -0400
Steven Rostedt wrote:
> On Tue, 20 Aug 2024 00:56:49 +0900
> Masami Hiramatsu (Google) wrote:
> >
> > >
> > > We may need to add "noinline" or something to make sure those functions
> > > don't get inlined for LTO.
> >
> > Yeah, we need such option at leas
On Tue, 20 Aug 2024 00:56:49 +0900
Masami Hiramatsu (Google) wrote:
>
> >
> > We may need to add "noinline" or something to make sure those functions
> > don't get inlined for LTO.
>
> Yeah, we need such option at least for function call test.
Could you add the noinline, and if it fixes the
On Mon, 19 Aug 2024 11:29:02 -0400
Steven Rostedt wrote:
> On Mon, 19 Aug 2024 17:11:52 +0900
> Masami Hiramatsu (Google) wrote:
>
> > CONFIG_LTO=y
> > CONFIG_LTO_CLANG=y
>
> Hi Masami,
>
> Does it still fail if you disable the above?
No, I found that caused these failure.
> I wonder if tha
On Mon, 19 Aug 2024 17:11:52 +0900
Masami Hiramatsu (Google) wrote:
> CONFIG_LTO=y
> CONFIG_LTO_CLANG=y
Hi Masami,
Does it still fail if you disable the above?
I wonder if that causes functions to not be part of the available filter
functions that the ftrace filter test is using :-/
We may ne
://syzkaller.appspot.com/bug?extid=bdb4bd87b5e22058e2a4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14a1b97d98
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e7b2f398
Reported-by: syzbot+bdb4bd87b5e22058e...@syzkaller.appspotmail.com
Fixes: 634f1a7110b4 ("
dashboard link: https://syzkaller.appspot.com/bug?extid=bdb4bd87b5e22058e2a4
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d4f4f598
C reproducer: https://syzkaller.appspot.com/x/repro.c?x
more recent versions as well?
Thanks,
Stefano
Stack dump:
BUG: TASK stack guard page was hit at c90001b27f88 (stack is
c90001b28000..c90001b3)
stack guard page: [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 PID: 8069 Comm: syz-executor293 Not tainted 6.8.0 #1
Hardware name: QEMU
Hello.
We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec.
Recently, our team has discovered a issue in Linux kernel 6.8. Attached to the
email were a PoC file of the issue.
Stack dump:
BUG: TASK stack guard page was hit at c90001b27f88 (stack is
c90001b28000
Hi,
On 2024/7/13 8:44, Jakub Kicinski wrote:
> On Fri, 12 Jul 2024 17:43:21 -0700 Jakub Kicinski wrote:
>> CC: virtio_net maintainers and Jiri who added BQL
>
> Oh, sounds like the fix may be already posted:
> https://lore.kernel.org/all/20240712080329.197605-2-jean-phili...@linaro.org/
Thanks,
On Fri, 12 Jul 2024 17:43:21 -0700 Jakub Kicinski wrote:
> CC: virtio_net maintainers and Jiri who added BQL
Oh, sounds like the fix may be already posted:
https://lore.kernel.org/all/20240712080329.197605-2-jean-phili...@linaro.org/
/linux-next.git and
> the base commit is f477dd6eede3
>
> >
> > [ cut here ]
> > kernel BUG at lib/dynamic_queue_limits.c:99!
> > Oops: invalid opcode: [#1] PREEMPT SMP NOPTI
> > CPU: 1 UID: 0 PID: 203 Comm: ip Not tainted
> > 6.10.0-rc7-
more free time.
--Ilkka
On Tue, Jun 18, 2024 at 5:52 PM Steven Rostedt wrote:
>
> On Thu, 13 Jun 2024 10:32:24 +0300
> Ilkka Naulapää wrote:
>
> > ok, so if you don't have any idea where this bug is after those debug
> > patches, I'll try to find some time t
On Thu, 13 Jun 2024 10:32:24 +0300
Ilkka Naulapää wrote:
> ok, so if you don't have any idea where this bug is after those debug
> patches, I'll try to find some time to bisect it as a last resort.
> Stay tuned.
FYI,
I just debugged a strange crash that was caused by my conf
o this? This thread looks stalled. I
>>> also was unsuccessful when looking for other threads related to this
>>> report or the culprit. Did it fall through the cracks or am I missing
>>> something here?
>
>> Honesty, I have no idea where the bug is. I can't reproduce
ok, so if you don't have any idea where this bug is after those debug
patches, I'll try to find some time to bisect it as a last resort.
Stay tuned.
--Ilkka
On Wed, Jun 12, 2024 at 6:56 PM Steven Rostedt wrote:
>
> On Wed, 12 Jun 2024 15:36:22 +0200
> "Linux regre
his thread looks stalled. I
> also was unsuccessful when looking for other threads related to this
> report or the culprit. Did it fall through the cracks or am I missing
> something here?
Honesty, I have no idea where the bug is. I can't reproduce it. These
patches I sent would check al
; --Ilkka
>
> On Thu, May 30, 2024 at 5:00 PM Steven Rostedt wrote:
>>
>> On Thu, 30 May 2024 16:02:37 +0300
>> Ilkka Naulapää wrote:
>>
>>> applied your patch and here's the output.
>>>
>>
>> Unfortunately, it doesn't g
On Thu, 30 May 2024 16:02:37 +0300
Ilkka Naulapää wrote:
> applied your patch and here's the output.
>
Unfortunately, it doesn't give me any new information. I added one more
BUG on, want to try this? Otherwise, I'm pretty much at a lost. :-/
-- Steve
diff --git a/fs
On Wed, 29 May 2024 14:47:57 -0400
Steven Rostedt wrote:
> Let me make a debug patch (that crashes on this issue) for that kernel,
> and perhaps you could bisect it?
Can you try this on 6.6-rc1 and see if it gives you any other splats?
Hmm, you can switch it to WARN_ON and that way it may not c
ent to the trace inode free list.
> this trace bug first triggered on 6.6-rc1.
Hmm, that's when eventfs was added.
>
> Let me know if you need more assistance with this.
Let me make a debug patch (that crashes on this issue) for that kernel,
and perhaps you could bisect it?
Thanks!
-- Steve
On Tue, 28 May 2024 07:51:30 +0300
Ilkka Naulapää wrote:
> yeah, the cache_from_obj tracing bug (without panic) has been
> displayed quite some time now - maybe even since 6.7.x or so. I could
> try checking a few versions back for this and try bisecting it if I
> can find when
yeah, the cache_from_obj tracing bug (without panic) has been
displayed quite some time now - maybe even since 6.7.x or so. I could
try checking a few versions back for this and try bisecting it if I
can find when this started.
--Ilkka
On Tue, May 28, 2024 at 1:31 AM Steven Rostedt wrote
ommit to 6.9.2 and now it only serves the trace but
> > > the panic is gone. But I can live with it.
> >
> > Steven, should we revert that?
> >
> > Or is there some other change that we should take to resolve this?
> >
>
> Before we revert it (as it may
On Fri, 24 May 2024 12:50:08 +0200
"Linux regression tracking (Thorsten Leemhuis)"
wrote:
> > - Affected Versions: Before kernel version 6.8.10, the bug caused a
> > quick display of a kernel trace dump before the shutdown/reboot
> > completed. Starting from versio
change that we should take to resolve this?
>
Before we revert it (as it may be a bug in mainline), Ilkka, can you
test v6.10-rc1? If it exists there, it will let me know whether or not
I missed something.
Thanks,
-- Steve
On Mon, May 27, 2024 at 07:40:21PM +0300, Ilkka Naulapää wrote:
> Hi Steven,
>
> I took some time and bisected the 6.8.9 - 6.8.10 and git gave the
> panic inducing commit:
>
> 414fb08628143 (tracefs: Reset permissions on remount if permissions are
> options)
>
> I reverted that commit to 6.9.2
n Leemhuis)"
> > wrote:
> >
> > > > - Affected Versions: Before kernel version 6.8.10, the bug caused a
> > > > quick display of a kernel trace dump before the shutdown/reboot
> > > > completed. Starting from version 6.8.10 and continuing into v
On Fri, 24 May 2024 12:50:08 +0200
"Linux regression tracking (Thorsten Leemhuis)"
wrote:
> > - Affected Versions: Before kernel version 6.8.10, the bug caused a
> > quick display of a kernel trace dump before the shutdown/reboot
> > completed. Starting from versio
On Fri, 24 May 2024 12:50:08 +0200
"Linux regression tracking (Thorsten Leemhuis)"
wrote:
> [CCing a few people]
>
Thanks for the Cc.
> On 24.05.24 12:31, Ilkka Naulapää wrote:
> >
> > I have encountered a critical bug in the Linux vanilla kernel that
> &g
[CCing a few people]
On 24.05.24 12:31, Ilkka Naulapää wrote:
>
> I have encountered a critical bug in the Linux vanilla kernel that
> leads to a kernel panic during the shutdown or reboot process. The
> issue arises after all services, including `journald`, have been
> stopped. A
On Wed, May 15, 2024 at 02:30:37PM -0700, Alexei Starovoitov wrote:
> On Tue, May 14, 2024 at 12:33 AM Ubisectech Sirius
> wrote:
> >
> > Hello.
> > We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec.
> > Recently, our team has discovered a issue in Linux kernel 6.7. Attach
On Tue, May 14, 2024 at 12:33 AM Ubisectech Sirius
wrote:
>
> Hello.
> We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec.
> Recently, our team has discovered a issue in Linux kernel 6.7. Attached to
> the email were a PoC file of the issue.
Jiri,
please take a look.
>
Hello.
We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec.
Recently, our team has discovered a issue in Linux kernel 6.7. Attached to the
email were a PoC file of the issue.
Stack dump:
loop3: detected capacity change from 0 to 8
MTD: Attempt to mount non-MTD device "/dev
d several of your others) are fixed in Linus's tree.
>
> Stack dump:
>
> bcachefs (loop1): mounting version 1.7: (unknown version)
> opts=metadata_checksum=none,data_checksum=none,nojournal_transaction_names
> ----[ cut here ]
> kernel BUG at fs/bcachefs
Hello.
We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec.
Recently, our team has discovered a issue in Linux kernel 6.7. Attached to the
email were a PoC file of the issue.
Stack dump:
BUG: unable to handle page fault for address: ed110c2fd97f
#PF: supervisor read
On Tue, 16 Apr 2024 04:08:46 +0200
Luca Ceresoli wrote:
> Thanks for the insight. I'm definitely trying to fix this based on your
> hint as soon as I get my hand on a board.
I have a patch I forgot to send out. Let me do that now.
-- Steve
Hello Steven,
On Mon, 15 Apr 2024 04:44:30 -0400
Steven Rostedt wrote:
> On Mon, 18 Mar 2024 16:43:07 +0100
> Luca Ceresoli wrote:
>
> > However the arrows are still reversed.
>
> This requires a kernel change. The problem is that the print fmt has:
>
> print fmt: "%c%s %s %s %s %s", (int)
On Mon, 18 Mar 2024 16:43:07 +0100
Luca Ceresoli wrote:
> However the arrows are still reversed.
This requires a kernel change. The problem is that the print fmt has:
print fmt: "%c%s %s %s %s %s", (int) REC->path_node && (int) REC->path_connect
? '*' : ' ', __get_str(wname), (((REC->path_dir)
ec025e18
> kernel config: https://syzkaller.appspot.com/x/.config?x=7b667bc37450fdcd
> dashboard link: https://syzkaller.appspot.com/bug?extid=689655a7402cc18ace0a
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
> 2.40
>
> Down
dashboard link: https://syzkaller.appspot.com/bug?extid=1f345d82b7f611cbcc66
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
2.40
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/26db68ddb08d/disk-623bdd58.raw.xz
vmlinux:
https
dashboard link: https://syzkaller.appspot.com/bug?extid=689655a7402cc18ace0a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
2.40
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/94b03853b65f/disk-6dae957c.raw.xz
vmlinux:
https
e9172
dashboard link: https://syzkaller.appspot.com/bug?extid=84f677a274bd8b05f6cb
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
2.40
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/89219dafdd42/disk-c1fd3a94.raw.xz
vmlinux:
Hi,
On the Ubuntu 22.04 LTS system, with recent iproute2-next toolsvand build
6.8-11743-ga4145ce1e7bc,
kmemleak system reported the following memory leaks:
unreferenced object 0x9da692e7e920 (size 16):
comm "modprobe", pid 2248188, jiffies 4358296226
hex dump (first 16 bytes):
68 6d 6d 5f 6
dashboard link: https://syzkaller.appspot.com/bug?extid=e58465c446f16bd6191a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
2.40
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/31c81b152208/disk-537c2e91.raw.xz
vmlinux:
https
x GOARCH=amd64 go build "-ldflags=-s -w -X
> github.com/google/syzkaller/prog.GitRevision=6753db5cdc04330ec9d1a5116b890c19481d69b3
> -X 'github.com/google/syzkaller/prog.gitRevisionDate=20240320-145051'"
> "-tags=syz_target syz_os_linux syz_arch_amd64 " -o
-than=16384 -Wno-stringop-overflow -Wno-array-bounds
-Wno-format-overflow -Wno-unused-but-set-variable
-Wno-unused-command-line-argument -static-pie -fpermissive -w -DGOOS_linux=1
-DGOARCH_amd64=1 \
-DHOSTGOOS_linux=1
-DGIT_REVISION=\"6753db5cdc04330ec9d1a5116b890c19481d69b3\"
Error
4bedfb31 mm,page_owner: maintain own list of stack_rec..
> git tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> kernel config: https://syzkaller.appspot.com/x/.config?x=527195e149aa3091
> dashboard link: https://syzkaller.appspot.com
/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=527195e149aa3091
dashboard link: https://syzkaller.appspot.com/bug?extid=70f57d8a3ae84934c003
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
2.40
Note: no patches were
ller.appspot.com/x/log.txt?x=10f04c8118
> >>> kernel config: https://syzkaller.appspot.com/x/.config?x=fcb5bfbee0a42b54
> >>> dashboard link:
> >>> https://syzkaller.appspot.com/bug?extid=70f57d8a3ae84934c003
> >>> compiler: Debian clang version 1
el.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=7b1f286a7e950707
dashboard link: https://syzkaller.appspot.com/bug?extid=70f57d8a3ae84934c003
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
2.40
Note: no pa
EAD commit:b3603fcb79b1 Merge tag 'dlm-6.9' of git://git.kernel.org/p..
>>> git tree: upstream
>>> console output: https://syzkaller.appspot.com/x/log.txt?x=10f04c8118
>>> kernel config: https://syzkaller.appspot.com/x/.config?x=fcb5bfbee0a42b54
&g
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
52998cdd8d3438df9a77c858a827b8932da1bb28
This is the last time virtio_scsi.c was touched. If the test passes then
the issue is probably in another subsystem and we can bisect more recent
commits. If it fails, then older v
nfig: https://syzkaller.appspot.com/x/.config?x=fcb5bfbee0a42b54
> > > dashboard link:
> > > https://syzkaller.appspot.com/bug?extid=70f57d8a3ae84934c003
> > > compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for
> > > Debian) 2.40
> > >
> > >
kernel.org/p..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=10f04c8118
> > kernel config: https://syzkaller.appspot.com/x/.config?x=fcb5bfbee0a42b54
> > dashboard link: https://syzkaller.appspot.com/bug?extid=70f57d8a3ae849
.com/x/log.txt?x=10f04c8118
> kernel config: https://syzkaller.appspot.com/x/.config?x=fcb5bfbee0a42b54
> dashboard link: https://syzkaller.appspot.com/bug?extid=70f57d8a3ae84934c003
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
> 2.40
>
bee0a42b54
dashboard link: https://syzkaller.appspot.com/bug?extid=70f57d8a3ae84934c003
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
2.40
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/43969dffd4a6/disk-b3603fcb.raw.xz
vmlin
On Mon, 18 Mar 2024 16:43:07 +0100
Luca Ceresoli wrote:
> Indeed I was on an older version, apologies.
>
> I upgraded both libtraceevent and trace-cmd to master and applied your
> patch, now the %c is formatted correctly.
>
> However the arrows are still reversed.
>
> Is this what you were exp
Hello Steven,
On Fri, 15 Mar 2024 14:58:52 -0400
Steven Rostedt wrote:
> On Fri, 15 Mar 2024 19:03:12 +0100
> Luca Ceresoli wrote:
>
> > > >
> > > > I've come across an unexpected behaviour in the kernel tracing
> > > > infrastructure that l
On Fri, 15 Mar 2024 19:03:12 +0100
Luca Ceresoli wrote:
> > >
> > > I've come across an unexpected behaviour in the kernel tracing
> > > infrastructure that looks like a bug, or maybe two.
> > >
> > > Cc-ing ASoC maintainers for as it appeared
nexpected behaviour in the kernel tracing
> > infrastructure that looks like a bug, or maybe two.
> >
> > Cc-ing ASoC maintainers for as it appeared using ASoC traces, but it
> > does not look ASoC-specific.
> >
> > It all started when using this
On Fri, 15 Mar 2024 17:49:00 +0100
Luca Ceresoli wrote:
> Hello Linux tracing maintainers,
Hi Luca!
>
> I've come across an unexpected behaviour in the kernel tracing
> infrastructure that looks like a bug, or maybe two.
>
> Cc-ing ASoC maintainers for as it appeared
Hello Linux tracing maintainers,
I've come across an unexpected behaviour in the kernel tracing
infrastructure that looks like a bug, or maybe two.
Cc-ing ASoC maintainers for as it appeared using ASoC traces, but it
does not look ASoC-specific.
It all started when using this trace-cmd seq
powerpc fixes from Michael Ellerman:
> "This is a bit of a big batch for rc4, but just due to holiday hangover
> and because I didn't send any fixes last week due to a late revert
> request. I think next week should be back to normal.
>
> Regards
> Le
/.config?x=4bc446d42a7d56c0
> > dashboard link: https://syzkaller.appspot.com/bug?extid=6f3c38e8a6a0297caa5a
> > compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for
> > Debian) 2.40
> >
> > Downloadable assets:
> > disk i
for 20240216
> > git tree: linux-next
> > console output: https://syzkaller.appspot.com/x/log.txt?x=171ca65218
> > kernel config: https://syzkaller.appspot.com/x/.config?x=4bc446d42a7d56c0
> > dashboard link: https://syzkaller.appspot.com/bug?extid=6f3c38e8a6a0297caa5a
&g
1ca65218
> kernel config: https://syzkaller.appspot.com/x/.config?x=4bc446d42a7d56c0
> dashboard link: https://syzkaller.appspot.com/bug?extid=6f3c38e8a6a0297caa5a
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
> 2.40
>
> Down
dashboard link: https://syzkaller.appspot.com/bug?extid=6f3c38e8a6a0297caa5a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
2.40
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/14d0894504b9/disk-d37e1e4c.raw.xz
vmlinux:
https
t?x=17659d2418
start commit: 453f5db0619e Merge tag 'trace-v6.7-rc7' of git://git.kerne..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f8e72bae38c079e4
dashboard link: https://syzkaller.appspot.com/bug?extid=f8a023e0c6beabe2371a
syz repr
Hello.
We are Ubisectech Sirius Team, the vulnerability lab of China ValiantSec.
Recently, our team has discovered a issue in Linux kernel 6.7.0-g052d534373b7.
Attached to the email were a POC file of the issue.
Stack dump:
[ 185.664167][ T8332] BUG: unable to handle page fault for address
g.txt?x=10ec3829e8
> kernel config: https://syzkaller.appspot.com/x/.config?x=f8e72bae38c079e4
> dashboard link: https://syzkaller.appspot.com/bug?extid=f8a023e0c6beabe2371a
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
> 2.40
> syz repro:
ae38c079e4
dashboard link: https://syzkaller.appspot.com/bug?extid=f8a023e0c6beabe2371a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian)
2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1414af31e8
C reproducer: https://syzkaller.appspot.com/x
On Tue, 02 Jan 2024 18:54:26 +0800
"Ubisectech Sirius" wrote:
> Dear concerned.
> Greetings!
> We are Ubisectech Sirius Team, the vulnerability lab of China
> ValiantSec.Recently, our team has discovered a issue in Linux kernel 6.7.
> technical details:
> 1. Vu
Hi,
On 12/21/2023 1:50 AM, Yonghong Song wrote:
>
> On 12/20/23 1:19 AM, Hou Tao wrote:
>> Hi,
>>
>> On 12/14/2023 11:40 AM, xingwei lee wrote:
>>> Hello I found a bug in net/bpf in the lastest upstream linux and
>>> comfired in the lastest net tree and
On 12/20/23 1:19 AM, Hou Tao wrote:
Hi,
On 12/14/2023 11:40 AM, xingwei lee wrote:
Hello I found a bug in net/bpf in the lastest upstream linux and
comfired in the lastest net tree and lastest net bpf titled BUG:
unable to handle kernel paging request in bpf_probe_read_compat_str
If you fix
Hi,
On 12/14/2023 11:40 AM, xingwei lee wrote:
> Hello I found a bug in net/bpf in the lastest upstream linux and
> comfired in the lastest net tree and lastest net bpf titled BUG:
> unable to handle kernel paging request in bpf_probe_read_compat_str
>
> If you fix this issue,
Hello I found a bug in net/bpf in the lastest upstream linux and
comfired in the lastest net tree and lastest net bpf titled BUG:
unable to handle kernel paging request in bpf_probe_read_compat_str
If you fix this issue, please add the following tag to the commit:
Reported-by: xingwei Lee
On Mon, Dec 11, 2023 at 02:01:43PM +0100, Jiri Olsa wrote:
> On Mon, Dec 11, 2023 at 07:29:40PM +0800, Hou Tao wrote:
>
> SNIP
>
> >
> > It seems a big attr->link_create.uprobe_multi.cnt is passed to
> > bpf_uprobe_multi_link_attach(). Could you please try the first patch in
> > the following pa
1 - 100 of 16677 matches
Mail list logo
