On 3/10/21 7:55 PM, Maxim Mikityanskiy wrote:
> On 2021-03-10 19:03, Eric Dumazet wrote:
>>
>>
>> On 3/10/21 3:54 PM, Maxim Mikityanskiy wrote:
>>> On 2021-03-09 17:20, Eric Dumazet wrote:
On 3/9/21 4:13 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue o
On 2021-03-10 19:03, Eric Dumazet wrote:
On 3/10/21 3:54 PM, Maxim Mikityanskiy wrote:
On 2021-03-09 17:20, Eric Dumazet wrote:
On 3/9/21 4:13 PM, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit: 38b5133a octeontx2-pf: Fix otx2_get_fecparam()
git tree: net-
On 3/10/21 3:54 PM, Maxim Mikityanskiy wrote:
> On 2021-03-09 17:20, Eric Dumazet wrote:
>>
>>
>> On 3/9/21 4:13 PM, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following issue on:
>>>
>>> HEAD commit: 38b5133a octeontx2-pf: Fix otx2_get_fecparam()
>>> git tree: net-next
>>> conso
On 2021-03-09 17:20, Eric Dumazet wrote:
On 3/9/21 4:13 PM, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit:38b5133a octeontx2-pf: Fix otx2_get_fecparam()
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=166288a8d0
kernel config
On 3/9/21 4:13 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:38b5133a octeontx2-pf: Fix otx2_get_fecparam()
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=166288a8d0
> kernel config: https://syzkaller.appspo
Hello,
syzbot found the following issue on:
HEAD commit:38b5133a octeontx2-pf: Fix otx2_get_fecparam()
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=166288a8d0
kernel config: https://syzkaller.appspot.com/x/.config?x=dbc1ca9e55dc1f9f
dashboard link: h
Eric Dumazet wrote:
>
>
> On 8/2/20 3:45 PM, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:ac3a0c84 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=1323
On 8/2/20 3:45 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:ac3a0c84 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1323497090
> kernel config: https://sy
Hello,
syzbot found the following issue on:
HEAD commit:ac3a0c84 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1323497090
kernel config: https://syzkaller.appspot.com/x/.config?x=c0cfcf935bcc94d2
das
Hello,
syzbot found the following crash on:
HEAD commit:cb8e59cc Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1446cfd310
kernel config: https://syzkaller.appspot.com/x/.config?x=a16ddbc78955e3a9
das
On 24. 09. 19 15:10, Michal Vokáč wrote:
On 24. 09. 19 14:31, Andrew Lunn wrote:
On Tue, Sep 24, 2019 at 01:27:24PM +0200, Michal Vokáč wrote:
Hi,
just tried booting latest next-20190920 on our imx6dl-yapp4-hydra platform
with QCA8334 switch and got this:
[7.424620] [<806840e0>] (phy_supp
On 24.09.2019 13:27, Michal Vokáč wrote:
> Hi,
>
> just tried booting latest next-20190920 on our imx6dl-yapp4-hydra platform
> with QCA8334 switch and got this:
>
> [ 6.957822] 8<--- cut here ---
> [ 6.963550] Unable to handle kernel NULL pointer dereference at virtual
> address 0264
On 25. 09. 19 2:44, Andrew Lunn wrote:
On Tue, Sep 24, 2019 at 03:10:44PM +0200, Michal Vokáč wrote:
On 24. 09. 19 14:31, Andrew Lunn wrote:
I added the printk and the above fix and can confirm that it is the CPU
port and the phy is NULL pointer:
[6.976366] qca8k 2188000.ethernet-1:0a: Usin
On Tue, Sep 24, 2019 at 03:10:44PM +0200, Michal Vokáč wrote:
> On 24. 09. 19 14:31, Andrew Lunn wrote:
> I added the printk and the above fix and can confirm that it is the CPU
> port and the phy is NULL pointer:
>
> [6.976366] qca8k 2188000.ethernet-1:0a: Using legacy PHYLIB callbacks.
> Pl
On 24. 09. 19 14:31, Andrew Lunn wrote:
On Tue, Sep 24, 2019 at 01:27:24PM +0200, Michal Vokáč wrote:
Hi,
just tried booting latest next-20190920 on our imx6dl-yapp4-hydra platform
with QCA8334 switch and got this:
[7.424620] [<806840e0>] (phy_support_asym_pause) from [<80686724>]
(qca8k_
On Tue, Sep 24, 2019 at 01:27:24PM +0200, Michal Vokáč wrote:
> Hi,
>
> just tried booting latest next-20190920 on our imx6dl-yapp4-hydra platform
> with QCA8334 switch and got this:
>
> [7.424620] [<806840e0>] (phy_support_asym_pause) from [<80686724>]
> (qca8k_port_enable+0x40/0x48)
> [
Hi,
just tried booting latest next-20190920 on our imx6dl-yapp4-hydra platform
with QCA8334 switch and got this:
[6.957822] 8<--- cut here ---
[6.963550] Unable to handle kernel NULL pointer dereference at virtual
address 0264
[6.974342] pgd = (ptrval)
[6.979751] [0264]
997647] IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
> > [ 274.054068] ip (11458) used greatest stack depth: 11448 bytes left
> > [ 274.120445] BUG: unable to handle kernel NULL pointer dereference
> > at
> > [ 274.128285] #PF error: [INSTR]
>
eatest stack depth: 11448 bytes left
> [ 274.120445] BUG: unable to handle kernel NULL pointer dereference
> at
> [ 274.128285] #PF error: [INSTR]
> [ 274.131351] PGD 800414a0e067 P4D 800414a0e067 PUD 3b6334067 PMD 0
> [ 274.138241] Oops: 0010 [#1] SM
Kernel panic while running bpf: test_tunnel.sh on linux -next
5.0.0-rc4-next-20190129.
selftests: bpf: test_tunnel.sh
[ 273.997647] IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
[ 274.054068] ip (11458) used greatest stack depth: 11448 bytes left
[ 274.120445] BUG: unable to handle
On Wed, Jan 2, 2019 at 4:51 PM Christopher Lameter wrote:
>
> On Wed, 2 Jan 2019, Dmitry Vyukov wrote:
>
> > Am I missing something or __alloc_alien_cache misses check for
> > kmalloc_node result?
> >
> > static struct alien_cache *__alloc_alien_cache(int node, int entries,
> >
On Wed, 2 Jan 2019, Dmitry Vyukov wrote:
> Am I missing something or __alloc_alien_cache misses check for
> kmalloc_node result?
>
> static struct alien_cache *__alloc_alien_cache(int node, int entries,
> int batch, gfp_t gfp)
> {
> size_t me
it_arraycache(&alc->ac, entries, batch);
spin_lock_init(&alc->lock);
return alc;
}
> BUG: unable to handle kernel NULL pointer dereference at 0038
> #PF error: [WRITE]
> PGD 8b2a5067 P4D 8b2a5067 PUD a53ed067 PMD 0
> Oops: 0002 [#1] PREEMPT S
rted-by: syzbot+d6ed4ec679652b4fd...@syzkaller.appspotmail.com
BUG: unable to handle kernel NULL pointer dereference at 0038
#PF error: [WRITE]
PGD 8b2a5067 P4D 8b2a5067 PUD a53ed067 PMD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 16188 Comm: syz-executor4 Not tainted 4.20.0+ #174
Hardwa
On Wed, May 2, 2018 at 10:44 PM, Andrew Morton
wrote:
> On Wed, 2 May 2018 21:58:25 -0700 Cong Wang wrote:
>
>> On Wed, May 2, 2018 at 9:27 PM, Andrew Morton
>> wrote:
>> >
>> > So it's saying that something which got committed into Linus's tree
>> > after 4.17-rc3 has caused a NULL deref in
>>
On Wed, 2 May 2018 21:58:25 -0700 Cong Wang wrote:
> On Wed, May 2, 2018 at 9:27 PM, Andrew Morton
> wrote:
> >
> > So it's saying that something which got committed into Linus's tree
> > after 4.17-rc3 has caused a NULL deref in
> > sock_release->llc_ui_release+0x3a/0xd0
>
> Do you mean it co
On Wed, May 2, 2018 at 9:27 PM, Andrew Morton wrote:
>
> So it's saying that something which got committed into Linus's tree
> after 4.17-rc3 has caused a NULL deref in
> sock_release->llc_ui_release+0x3a/0xd0
Do you mean it contains commit 3a04ce7130a7
("llc: fix NULL pointer deref for SOCK_ZAPP
; [many lines deleted]
>
> [main] Setsockopt(101 c 1b24000 a) on fd 177 [3:5:240]
> [main] Setsockopt(1 2c 1b24000 4) on fd 178 [5:2:0]
> [main] Setsockopt(29 8 1b24000 4) on fd 180 [10:1:0]
> [main] Setsockopt(1 20 1b24000 4) on fd 181 [26:2:125]
> [main] Setsockopt(11 1 1b24000 4) o
cachefile.
[main] Generating file descriptors
[main] Added 83 filenames from /dev
udevd[507]: failed to execute '/sbin/modprobe' '/sbin/modprobe -bv
platform:regulatory': No such file or directory
[ 372.057947] caif:caif_disconnect_client(): nothing to disconnect
[ 372.082415] B
t; [main] Added 83 filenames from /dev
> udevd[507]: failed to execute '/sbin/modprobe' '/sbin/modprobe -bv
platform:regulatory': No such file or directory
> [ 372.057947] caif:caif_disconnect_client(): nothing to disconnect
> [ 372.082415] BUG: unable to handle kernel
Hi,
syzkaller found a null pointer in read_pnet on 4.4.128 (Latest LTS).
Unfortunately I don't have a repo code for now. Will post and test
on the top of the tree if available.
Due to my testing env (Android), cannot run Linus top of the tree.
Could be related to https://www.spinics.net/lists/ne
On Tue, 2018-04-10 at 15:53 +0300, Igor Russkikh wrote:
> On 10.04.2018 15:42, Yanko Kaneti wrote:
> > Hello,
> >
> > Since 90869ddfefeb net: aquantia: Implement pci shutdown callback
> > I get the below oops on reboot. Without the callback everything works
> > as expected.
> >
>
> Thanks, we
On 10.04.2018 15:42, Yanko Kaneti wrote:
> Hello,
>
> Since 90869ddfefeb net: aquantia: Implement pci shutdown callback
> I get the below oops on reboot. Without the callback everything works
> as expected.
>
Thanks, we also recently found out that.
Could you please try the below patch?
di
rawhide config - atlantic is a module.
[ 6278.083643] BUG: unable to handle kernel NULL pointer dereference at
0058
[ 6278.091536] PGD 0 P4D 0
[ 6278.094113] Oops: [#1] SMP NOPTI
[ 6278.097802] Modules linked in: nfsv3 nfs_acl nfs lockd grace fscache pppoe
pppox ppp_synctty
; kfree(stream->out);
> > > stream->out = NULL;
> > > + stream->outcnt = 0;
> > > out:
> > > return ret;
> > > }
> >
> > In case it can't be verified due to no reproducer yet, I modified some
>
; code in sctp_stream_init() to confirm Marcelo's deduction:
> - i = sctp_stream_alloc_in(stream, incnt, gfp);
> + i = 1;
> if (i) {
> ret = -ENOMEM;
> goto free;
>
> And got the same call trace as the mail:
>
23647:23660 DecRefs 0 refcount change on invalid ref 4 ret -22
> > binder: 23647:23660 BC_CLEAR_DEATH_NOTIFICATION invalid ref 0
> > binder: 23647:23660 BC_REQUEST_DEATH_NOTIFICATION invalid ref 3
> > binder: 23647:23660 got reply transaction with no transaction stack
> > binder: 23647:23660 t
On (01/30/18 14:22), Eric Biggers wrote:
>
> I assume you weren't able to reproduce this? This crash hasn't been
> seen again,
:
> I am invalidating the bug for syzbot so it will report the same crash
> signature
> again if it occurs, but if you think there is a real bug feel free to keep
> loo
On Mon, Dec 18, 2017 at 12:22:51PM -0500, Sowmini Varadhan wrote:
> > From: Santosh Shilimkar
> > Date: Mon, 18 Dec 2017 08:28:05 -0800
> :
> > > Looks like another one tripping on empty transport. Mostly below
> > > should
> > > address it but we will test it if it does.
>
> that was my first
ttached
> Raw console output is attached.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> BUG: unable to handle kernel NULL pointer dereference at 022c
> IP: inet6_fill_ifinfo+0x8e/0x2c0 net/ipv6/addrconf.c:5357
> PGD 1dffd8067 P4D 1
ttached
> Raw console output is attached.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> BUG: unable to handle kernel NULL pointer dereference at 0578
> IP: read_pnet include/net/net_namespace.h:270 [inline]
> IP: de
ttached
> Raw console output is attached.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> netlink: 29 bytes leftover after parsing attributes in process
> `syz-executor2'.
> device eql entered promiscuous mode
> BUG: unable to handl
ttached
> Raw console output is attached.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> BUG: unable to handle kernel NULL pointer dereference at (null)
> IP: qdisc_dev include/net/sch_generic.h:379 [inline]
> IP: tc_fill_qdisc+0xc8
ttached
> Raw console output is attached.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> netlink: 1 bytes leftover after parsing attributes in process
> `syz-executor6'.
> BUG: unable to handle kernel NULL pointer dereference at
ttached
> Raw console output is attached.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> device lo entered promiscuous mode
> device lo left promiscuous mode
> BUG: unable to handle kernel NULL pointer dereference at 0328
> IP:
ttached
> Raw console output is attached.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> netlink: 3 bytes leftover after parsing attributes in process
> `syz-executor5'.
> netlink: 3 bytes leftover after parsing attributes in process
ttached
> Raw console output is attached.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> ALSA: seq fatal error: cannot create timer (-22)
> device syz2 entered promiscuous mode
> BUG: unable to handle kernel NULL pointer dereference at
:23660 BC_REQUEST_DEATH_NOTIFICATION invalid ref 3
> binder: 23647:23660 got reply transaction with no transaction stack
> binder: 23647:23660 transaction failed 29201/-71, size 24-16 line 2747
> BUG: unable to handle kernel NULL pointer dereference at 0078
> IP: sctp_cmp_add
ttached
> Raw console output is attached.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> BUG: unable to handle kernel NULL pointer dereference at (null)
> IP: addrconf_ifdown+0x3a2/0x780 net/ipv6/addrconf.c:3674
> PGD 1df99c067 P4D 1
fied some
code in sctp_stream_init() to confirm Marcelo's deduction:
- i = sctp_stream_alloc_in(stream, incnt, gfp);
+ i = 1;
if (i) {
ret = -ENOMEM;
goto free;
And got the same call trace as the mail:
[ 301.488065] BUG: unable to handle ke
> From: Santosh Shilimkar
> Date: Mon, 18 Dec 2017 08:28:05 -0800
:
> > Looks like another one tripping on empty transport. Mostly below
> > should
> > address it but we will test it if it does.
that was my first thought, but it cannot be the case here: rds_sendmsg
etc itself would have bombed
-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.
Unfortunately, I don't have any reproducer for this bug yet.
BUG: unable to handle kernel NULL pointer dereference at
0028
program syz-executor6 is using a deprecated SCSI ioctl, p
aster
>> compiler: gcc (GCC) 7.1.1 20170620
>> .config is attached
>> Raw console output is attached.
>> Unfortunately, I don't have any reproducer for this bug yet.
>> BUG: unable to handle kernel NULL pointer dereference at
>> 0028
>> progr
.
Unfortunately, I don't have any reproducer for this bug yet.
BUG: unable to handle kernel NULL pointer dereference at 0028
program syz-executor6 is using a deprecated SCSI ioctl, please convert
it to SG_IO
IP: rds_send_xmit+0x80/0x930 net/rds/send.c:186
Looks like another one trippi
On (12/18/17 00:43), syzbot wrote:
> BUG: unable to handle kernel NULL pointer dereference at 0028
> program syz-executor6 is using a deprecated SCSI ioctl, please convert it to
> SG_IO
> IP: rds_send_xmit+0x80/0x930 net/rds/send.c:186
conn->c_trans is at offset 0x28.
today we get this bug:
>>>>
>>>> The kernel version is 4.15.0-rc3-next-20171215
>>>>
>>>> [ 235.397328] BUG: unable to handle kernel NULL pointer dereference
>>>> at 000c
>>>> [ 235.398624] IP: fdb_find_rcu+0x
is 4.15.0-rc3-next-20171215
>>>
>>> [ 235.397328] BUG: unable to handle kernel NULL pointer dereference
>>> at 000c
>>> [ 235.398624] IP: fdb_find_rcu+0x3c/0x130
>> [snip]
>>
>> Hi,
>> Thanks for the report, I've missed the
On 16/12/17 11:17, Nikolay Aleksandrov wrote:
> On 16/12/17 02:37, Andrei Vagin wrote:
>> Hi,
>>
>> We run criu tests for linux-next and today we get this bug:
>>
>> The kernel version is 4.15.0-rc3-next-20171215
>>
>> [ 235.397328] BUG: unable to
On 16/12/17 02:37, Andrei Vagin wrote:
> Hi,
>
> We run criu tests for linux-next and today we get this bug:
>
> The kernel version is 4.15.0-rc3-next-20171215
>
> [ 235.397328] BUG: unable to handle kernel NULL pointer dereference
> at 000c
> [ 235.39
Hi,
We run criu tests for linux-next and today we get this bug:
The kernel version is 4.15.0-rc3-next-20171215
[ 235.397328] BUG: unable to handle kernel NULL pointer dereference
at 000c
[ 235.398624] IP: fdb_find_rcu+0x3c/0x130
[ 235.399365] PGD 51970067 P4D 51970067 PUD
On Sun, Dec 03, 2017 at 04:37:01AM -0800, syzbot wrote:
> BUG: KASAN: use-after-free in skcipher_request_set_tfm
> include/crypto/skcipher.h:499 [inline]
> BUG: KASAN: use-after-free in crypto_aead_copy_sgl crypto/algif_aead.c:85
> [inline]
> BUG: KASAN: use-after-free in _aead_recvmsg crypto/algif
On Tue, 2016-11-15 at 06:02 -0800, Eric Dumazet wrote:
> On Tue, 2016-11-15 at 10:26 +0100, Paolo Abeni wrote:
> > Hi,
> >
> > On Mon, 2016-11-14 at 15:24 -0800, Andrei Vagin wrote:
> > > Our test system detected a kernel oops. Looks like a problem in the
> > > "udp: refactor memory accounting" se
On Tue, 2016-11-15 at 10:26 +0100, Paolo Abeni wrote:
> Hi,
>
> On Mon, 2016-11-14 at 15:24 -0800, Andrei Vagin wrote:
> > Our test system detected a kernel oops. Looks like a problem in the
> > "udp: refactor memory accounting" series.
>
> My fault: I missed udplite in my tests.
>
> Thank you f
Hi,
On Mon, 2016-11-14 at 15:24 -0800, Andrei Vagin wrote:
> Our test system detected a kernel oops. Looks like a problem in the
> "udp: refactor memory accounting" series.
My fault: I missed udplite in my tests.
Thank you for reporting.
I'm fine with Eric's patch, setting both .memory_allocate
On Mon, 2016-11-14 at 16:31 -0800, Eric Dumazet wrote:
> On Mon, 2016-11-14 at 15:58 -0800, Andrei Vagin wrote:
>
> >
> > Yes, you are right. It works if we set .memory_allocated and .sysctl_mem.
>
> Now the question would be :
>
> Are we okay if UDP and UDPlite share the same limits ?
>
> I w
On Mon, 2016-11-14 at 15:58 -0800, Andrei Vagin wrote:
>
> Yes, you are right. It works if we set .memory_allocated and .sysctl_mem.
Now the question would be :
Are we okay if UDP and UDPlite share the same limits ?
I would vote for yes, because these default limits are huge anyway
(The 50% re
step and
850cbaddb52dfd4e0c7cabe2c168dd34b44ae0b9 is the first bad commit.
> # first bad commit: [a10b91b8b81c29b87ff5a6d58c1402898337b956] Merge
> branch 'udpmem'
>
>
> [ 112.472363] BUG: unable to handle kernel NULL pointer dereference
> at (null)
> [ 112.4733
wn
>> memory accounting schema
>> git bisect good 850cbaddb52dfd4e0c7cabe2c168dd34b44ae0b9
>> # first bad commit: [a10b91b8b81c29b87ff5a6d58c1402898337b956] Merge
>> branch 'udpmem'
>>
>>
>> [ 112.472363] BUG: unable to handle kernel NULL pointer
On Mon, 2016-11-14 at 15:35 -0800, Eric Dumazet wrote:
>
> Thanks for the report.
>
> I guess following patch would be needed ?
>
> diff --git a/net/ipv4/udplite.c b/net/ipv4/udplite.c
> index
> af817158d830c0da080935ba29e012dffbb89112..12604c0371c451efcc9aad278bb86be9ac4bb813
> 100644
> ---
ad commit: [a10b91b8b81c29b87ff5a6d58c1402898337b956] Merge
> branch 'udpmem'
>
>
> [ 112.472363] BUG: unable to handle kernel NULL pointer dereference
> at (null)
> [ 112.473360] IP: [] __sk_mem_raise_allocated+0x31/0x3f0
> [ 112.474156] PGD 62a08067 [ 112.474455]
402898337b956
# good: [850cbaddb52dfd4e0c7cabe2c168dd34b44ae0b9] udp: use it's own
memory accounting schema
git bisect good 850cbaddb52dfd4e0c7cabe2c168dd34b44ae0b9
# first bad commit: [a10b91b8b81c29b87ff5a6d58c1402898337b956] Merge
branch 'udpmem'
[ 112.472363] BUG: unable to handle kernel NULL pointer dereferenc
m /dev
[ 56.590952] BUG: unable to handle kernel NULL pointer dereference at 0c40
[ 56.598975] IP: [<790e4f29>] perf_prepare_sample+0x229/0x330
[ 56.599783] *pde =
[ 56.601158] Oops: [#1] SMP
[ 56.604020] CPU: 1 PID: 398 Comm: trinity-main Not tainted
4.6.0-rc4-00181
Le Sun, 21 Oct 2007 13:16:32 +0800,
Coly Li <[EMAIL PROTECTED]> a écrit :
> > This should be fixed in recent git by
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9b013e05e0289c190a53d78ca029e2f21c0e4485
> >
> Maybe we encounter same condition, at least the symbol
Guillaume Chazarain wrote:
>>> BUG: unable to handle kernel NULL pointer dereference at virtual address
>>> 0004
>
> This should be fixed in recent git by
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9b013e05e0289c190a53d78ca
> > BUG: unable to handle kernel NULL pointer dereference at virtual address
> > 0004
This should be fixed in recent git by
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9b013e05e0289c190a53d78ca029e2f21c0e4485
HTH.
--
Guillaume
-
To unsubscri
added some relevant CCs
On Sat, 20 Oct 2007, Dave Haywood wrote:
> BUG: unable to handle kernel NULL pointer dereference at virtual address
> 0004
>
> Linux s1 2.6.23-g4fa4d23f #4 Fri Oct 19 10:15:50 BST 2007 i686 Pentium III
> (Coppermine) GenuineIntel GNU/L
On Thu, 18 Oct 2007, Patrick McHardy wrote:
Krzysztof Oledzki wrote:
Hum, you are using IPT_TPROXY thing, which is not in linux-2.6.22.9
It is only compiled in, not used at the moment.
But at least the previous version (before those patches posted a week
ago) touches the routing code in e
Krzysztof Oledzki wrote:
Hum, you are using IPT_TPROXY thing, which is not in linux-2.6.22.9
It is only compiled in, not used at the moment.
But at least the previous version (before those patches posted a week
ago) touches the routing code in exactly that function.
-
To unsubscribe from this
On Wed, 17 Oct 2007, Eric Dumazet wrote:
Krzysztof Oledzki a écrit :
On Wed, 17 Oct 2007, Eric Dumazet wrote:
Krzysztof Oledzki a écrit :
On Wed, 17 Oct 2007, Eric Dumazet wrote:
Krzysztof Oledzki a écrit :
Hello,
Today I found in my logs:
BUG: unable to handle kernel NULL
Krzysztof Oledzki a écrit :
On Wed, 17 Oct 2007, Eric Dumazet wrote:
Krzysztof Oledzki a écrit :
On Wed, 17 Oct 2007, Eric Dumazet wrote:
Krzysztof Oledzki a écrit :
Hello,
Today I found in my logs:
BUG: unable to handle kernel NULL pointer dereference at virtual
address 00b0
On Wed, 17 Oct 2007, Eric Dumazet wrote:
Krzysztof Oledzki a écrit :
On Wed, 17 Oct 2007, Eric Dumazet wrote:
Krzysztof Oledzki a écrit :
Hello,
Today I found in my logs:
BUG: unable to handle kernel NULL pointer dereference at virtual address
00b0
printing eip:
78395f65
*pde
Krzysztof Oledzki a écrit :
On Wed, 17 Oct 2007, Eric Dumazet wrote:
Krzysztof Oledzki a écrit :
Hello,
Today I found in my logs:
BUG: unable to handle kernel NULL pointer dereference at virtual
address 00b0
printing eip:
78395f65
*pde =
Oops: [#1]
PREEMPT SMP
CPU
On Wed, 17 Oct 2007, Eric Dumazet wrote:
Krzysztof Oledzki a écrit :
Hello,
Today I found in my logs:
BUG: unable to handle kernel NULL pointer dereference at virtual address
00b0
printing eip:
78395f65
*pde =
Oops: [#1]
PREEMPT SMP
CPU:0
EIP:0060:[<78395
Krzysztof Oledzki a écrit :
Hello,
Today I found in my logs:
BUG: unable to handle kernel NULL pointer dereference at virtual address
00b0
printing eip:
78395f65
*pde =
Oops: [#1]
PREEMPT SMP
CPU:0
EIP:0060:[<78395f65>]Not tainted VLI
EFLAGS: 00
Hello,
Today I found in my logs:
BUG: unable to handle kernel NULL pointer dereference at virtual address
00b0
printing eip:
78395f65
*pde =
Oops: [#1]
PREEMPT SMP
CPU:0
EIP:0060:[<78395f65>]Not tainted VLI
EFLAGS: 00210286 (2.6.22.9 #1)
EIP
Hi Mark,
[Adding netdev to CC]
On 07/09/2007, Mark Nipper <[EMAIL PROTECTED]> wrote:
> I've received two oopses now from my kernel while running
> the 2.6.22 series. The first was with 2.6.22.1 back in July and
> the second which happened just within the last day is 2.6.22.5.
> They both
hanging).
> If I'm lucky the Oops below makes it to my syslog (unfortunately SysRq-{p,s,i}
> doesn't work when it hangs, neither can I ssh into it):
>
> Aug 18 19:47:41 draco kernel: BUG: unable to handle kernel NULL pointer
> dereference at virtual address
> Aug 18
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> You have tcp_v6 lockdep warnings. They're in
> http://xml.cweiske.de/dojo%20kernelpanic%20+%20debug.tar.bz2 is anyone is
> keen. (I've largely lost interest in lockdep warnings - many of them are
> false positives and require make-lockdep-shut-up pat
r: [<3000>](0x3000)
000: 00 00 00 10 a2 08 c6 a8 a5 08 c6 46 3a 00 00 10
010: 10 41 c0 bc a2 08 c6 20 d3 60 c0 00 00 00 00 00
slab error in cache_alloc_debugcheck_after(): cache `ip_conntrack': double freen
[] show_trace+0x19/0x20
[] dump_stack+0x1a/0x20
[] __slab_error+0x21/0x30
[
89 matches
Mail list logo
