Skip to contentSkip to conversation

BUG: unable to handle kernel paging request in ipcget

DISCUSSION Manfred Spraul 3 participants 4 messages Dec 23, 2017 – Jan 7, 2018 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi,

Quoted 10 lines · syzbot

Hello,

syzkaller hit the following crash on 6084b576dca2e898f5c101baef151f7bfdbb606d
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-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.

Is one of the recent issues reproducible?
Either something is wrong with the faster ipc_get, or the improved ipc_get makes issues in other areas visible.

--
    Manfred

#2 lore raw
Quoted 13 lines · Manfred Spraul

Hi,

Quoted 10 lines · syzbot

Hello,

syzkaller hit the following crash on
6084b576dca2e898f5c101baef151f7bfdbb606d
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

Quoted 3 lines
Quoted 2 lines

Unfortunately, I don't have any reproducer for this bug yet.

Is one of the recent issues reproducible?

Which one do you mean?
syzbot always provides up-to-date status of reproducers for all reported bugs.

Quoted 13 lines

Either something is wrong with the faster ipc_get, or the improved ipc_get makes issues in other areas visible.

--
Manfred

--
You received this message because you are subscribed to the Google Groups "syzkaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

For more options, visit https://groups.google.com/d/optout.

#3 lore raw
Quoted 15 lines · Dmitry Vyukov
Quoted 13 lines · Manfred Spraul

Hi,

Quoted 10 lines · syzbot

Hello,

syzkaller hit the following crash on
6084b576dca2e898f5c101baef151f7bfdbb606d
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

Quoted 20 lines
Quoted 3 lines
Quoted 2 lines

Unfortunately, I don't have any reproducer for this bug yet.

Is one of the recent issues reproducible?

Which one do you mean?
syzbot always provides up-to-date status of reproducers for all reported bugs.

Quoted 13 lines

Either something is wrong with the faster ipc_get, or the improved ipc_get makes issues in other areas visible.

--
Manfred

--
You received this message because you are subscribed to the Google Groups "syzkaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

For more options, visit https://groups.google.com/d/optout.

Was this report related to the recent set of kmalloc-1024 false positives?

-Kees

Signature · 2 lines
Kees Cook
Pixel Security
#4 lore raw
Quoted 20 lines · Kees Cook
Quoted 19 lines · Dmitry Vyukov
Quoted 16 lines · Manfred Spraul

Hi,

Quoted 12 lines · syzbot

Hello,

syzkaller hit the following crash on
6084b576dca2e898f5c101baef151f7bfdbb606d
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-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.

Is one of the recent issues reproducible?

Quoted 7 lines
Quoted 5 lines

Which one do you mean?
syzbot always provides up-to-date status of reproducers for all reported bugs.

Quoted 2 lines

Either something is wrong with the faster ipc_get, or the improved ipc_get makes issues in other areas visible.

Was this report related to the recent set of kmalloc-1024 false positives?

That's possible. It happened only twice and is unexplainable (right?). Let's do:

#syz fix: crypto: pcrypt - fix freeing pcrypt instances

and see if this happens again after the commit lands.