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
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)
> [
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
On Wed, Jan 2, 2019 at 12:36 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:903b77c63167 Merge tag 'linux-kselftest-4.21-rc1' of git:/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=133428e340
> kernel config:
On Tue, Jan 30, 2018 at 03:03:50PM -0800, Eric Biggers wrote:
> On Fri, Dec 22, 2017 at 01:31:26PM +0800, Xin Long wrote:
> > On Thu, Dec 21, 2017 at 9:13 PM, Marcelo Ricardo Leitner
> > wrote:
> > > On Wed, Dec 20, 2017 at 12:51:01PM -0800, syzbot wrote:
> > >
> > > from the log:
> > > [ 89.451
On Fri, Dec 22, 2017 at 01:31:26PM +0800, Xin Long wrote:
> On Thu, Dec 21, 2017 at 9:13 PM, Marcelo Ricardo Leitner
> wrote:
> > On Wed, Dec 20, 2017 at 12:51:01PM -0800, syzbot wrote:
> >
> > from the log:
> > [ 89.451366] FAULT_INJECTION: forcing a failure.^M
> > [ 89.451366] name failslab,
On Tue, Jan 30, 2018 at 01:57:44PM -0800, Eric Biggers wrote:
> On Tue, Dec 19, 2017 at 11:49:03PM -0800, syzbot wrote:
> > Hello,
> >
> > syzkaller hit the following crash on
> > 6084b576dca2e898f5c101baef151f7bfdbb606d
> > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
On Mon, Dec 18, 2017 at 11:54:00PM -0800, syzbot wrote:
> 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 o
On Tue, Dec 19, 2017 at 12:35:02AM -0800, syzbot wrote:
> 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 o
On Tue, Dec 19, 2017 at 12:40:01AM -0800, syzbot wrote:
> 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 o
On Tue, Dec 19, 2017 at 04:49:02AM -0800, syzbot wrote:
> 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 o
On Tue, Dec 19, 2017 at 05:43:00AM -0800, syzbot wrote:
> 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 o
On Tue, Dec 19, 2017 at 08:38:01AM -0800, syzbot wrote:
> 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 o
On Tue, Dec 19, 2017 at 10:41:00AM -0800, syzbot wrote:
> 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 o
On Tue, Dec 19, 2017 at 11:48:01AM -0800, syzbot wrote:
> 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 o
On Tue, Dec 19, 2017 at 11:49:03PM -0800, syzbot wrote:
> 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 o
On Tue, Dec 19, 2017 at 11:50:01PM -0800, syzbot wrote:
> 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 o
On Thu, Dec 21, 2017 at 9:13 PM, Marcelo Ricardo Leitner
wrote:
> On Wed, Dec 20, 2017 at 12:51:01PM -0800, syzbot wrote:
>
> from the log:
> [ 89.451366] FAULT_INJECTION: forcing a failure.^M
> [ 89.451366] name failslab, interval 1, probability 0, space 0,
> times 0^M
> [ 89.451374] CPU: 0
On 12/18/2017 9:12 AM, David Miller wrote:
From: Santosh Shilimkar
Date: Mon, 18 Dec 2017 08:28:05 -0800
On 12/18/2017 12:43 AM, syzbot wrote:
Hello,
syzkaller hit the following crash on
6084b576dca2e898f5c101baef151f7bfdbb606d
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
From: Santosh Shilimkar
Date: Mon, 18 Dec 2017 08:28:05 -0800
> On 12/18/2017 12:43 AM, syzbot wrote:
>> 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.
On 12/18/2017 12:43 AM, syzbot wrote:
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.
Unfortunat
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.
Both this and ht
On 16/12/17 12:40, Nikolay Aleksandrov wrote:
> On 16/12/17 11:29, Nikolay Aleksandrov wrote:
>> 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.
On 16/12/17 11:29, Nikolay Aleksandrov wrote:
> 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: unab
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 handle kernel NULL pointer dereference
>> at 0
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.398624] IP: fdb_find_rcu+0x3c/0x
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 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 pointer
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
p
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:[<78395f65>]
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: 00210286 (2.6.22.
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
[Adding netdev to CC]
On 21/08/07, poison <[EMAIL PROTECTED]> wrote:
> Hello,
> after running a few instances of bittorent-curses on 2.6.22 - 2.6.22.3 it
> takes about 15min to 2hrs for my System to hang. 2.6.21.7 is definately fine,
> 2.6.21 probably (ran for 4hrs without hanging).
> If I'm lucky
44 matches
Mail list logo
