Phil writes:
> Hi, I hope you're all doing well.
>
> Shall we/I maybe reopen a new issue?
I believe so. I am almost sure we fixed the original memset BUG in
cdc_ncm_fill_tx_frame. Or at least one of them...
So you are probably seeing another issue if you still have problems with
that fix in
Hi, I hope you're all doing well.
Shall we/I maybe reopen a new issue?
I'm still affected by this and I'd could use some advice how to debug
the issue a little bit better, especially since the kexec kernel
crashdumps appear not to be helpful. Can I maybe compile the module with
special debug
On 08/04/2018 02:04 PM, Горбешко Богдан wrote:
Unfortunately, I messed with it for several hours but couldn't reproduce
the bug intentionally.
I've just launched a long living rsync job and streamed a video via. mpv
and managed to crash my system this way.
Before the crash I managed to upload
Unfortunately, I messed with it for several hours but couldn't reproduce
the bug intentionally. Does anyone have any hints on how to do this more
reliably? I tried to upload several files simultaneously, to fill the
memory with tmpfs partitions for emulating high memory pressure
condition, but
I upgraded the kernel to 4.17.8 and experienced the issue again. Not
sure if the bug is the same technically, but the sympthomes are: I tried
to upload a 30 MB file, and in the midst got a noisy screen. I will try
to catch it with kdump to get the backtrace again later.
On 6/29/18 11:17 AM,
On Fri, 29 Jun 2018 10:17:20 +0200 =?utf-8?Q?Bj=C3=B8rn_Mork?=
wrote:
> This issue should be fixed by commit
> 49c2c3f246e2 ("cdc_ncm: avoid padding beyond end of skb")
> https://patchwork.kernel.org/patch/10453923/
> Please check again with one of those kernel versions (or newer).
Hi, thank
This issue should be fixed by commit
49c2c3f246e2 ("cdc_ncm: avoid padding beyond end of skb")
which has been backported to v4.17.3, v4.16.18 and v4.14.52. Please
check again with one of those kernel versions (or newer).
I see now that the fix doesn't apply cleanly to v4.9 stable due to
Hi everybody,
I'm really greatful about stumbling upon this issue, because it
describes the exact same issue I've been experiencing for a while now.
Basically whenever I upload file/s via. rsync/Firefox/Chromium, within
several seconds my entire Linux system crashes. I've experienced this
On 3/19/18 2:18 AM, Bjørn Mork wrote:
Горбешко Богдан writes:
vboxdrv(O)
binder_linux(O)
ashmem_linux(O)
Can you reproduce the problem without these modules loaded?
ashmem/binder were installed only 3 weeks ago. And Virtualbox VMs were
run last time in July 2017,
Горбешко Богдан writes:
> vboxdrv(O)
> binder_linux(O)
> ashmem_linux(O)
Can you reproduce the problem without these modules loaded?
AFAICS there is no way the only memset in cdc_ncm can be called with
crashing input parameters. Unless something is scribbling over the
Package: linux-image-amd64
Version: 4.14+89
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
This bothers me from November 2017, when wvdial broke and I moved to
NetworkManager. While wvdial uses only serial interface (ttyUSB),
NetworkManager sometimes recognizes the
11 matches
Mail list logo