> On Monday, 12 February 2024 11:26:24 CET syzbot wrote:
>> syzbot found the following issue on:
>>
>> HEAD commit:41bccc98fb79 Linux 6.8-rc2
>> git tree:
>> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
>> console output:
On Monday, 12 February 2024 11:26:24 CET syzbot wrote:
> syzbot found the following issue on:
>
> HEAD commit:41bccc98fb79 Linux 6.8-rc2
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> for-kernelci
> console output:
On Mon, Feb 12, 2024 at 11:26 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:41bccc98fb79 Linux 6.8-rc2
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> for-kernelci
> console output:
On Monday, 12 February 2024 11:41:38 CET Eric Dumazet wrote:
> This patch [1] looks suspicious
Shouldn't be caused by this - but this might be another way to trigger the
problem. The problem would be visible even without it when a mtu is explicitly
set. But the reproducer is not available so I
Hello,
syzbot found the following issue on:
HEAD commit:41bccc98fb79 Linux 6.8-rc2
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1420011818
kernel config:
