From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: anon anon <742991625abc@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Petr Mladek <pmladek@suse.com>,
wangkefeng.wang@huawei.com, syzkaller@googlegroups.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: KASAN: slab-out-of-bounds Write in vgacon_scroll
Date: Wed, 29 Jan 2020 23:40:52 +0900 [thread overview]
Message-ID: <20200129143754.GA15445@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20200129141759.GB13721@jagdpanzerIV.localdomain>
Cc-ing Dmitry and Tetsuo
Original Message-id: CAA=061EoW8AmjUrBLsJy5nTDz-1jeArLeB+z6HJuyZud0zZXug@mail.gmail.com
On (20/01/29 23:17), Sergey Senozhatsky wrote:
> > Hmm. There is something strange about it. I use vga console quite
> > often, and scrolling happens all the time, yet I can't get the same
> > out-of-bounds report (nor have I ever seen it in the past), even with
> > the reproducer. Is it supposed to be executed as it is, or are there
> > any preconditions? Any chance that something that runs prior to that
> > reproducer somehow impacts the system? Just asking.
>
> These questions were addressed to anon anon (742991625abc@gmail.com),
> not to Bartlomiej.
Could this be GCC_PLUGIN related?
-ss
next prev parent reply other threads:[~2020-01-29 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA=061EoW8AmjUrBLsJy5nTDz-1jeArLeB+z6HJuyZud0zZXug@mail.gmail.com>
2020-01-28 12:49 ` Petr Mladek
2020-01-28 14:58 ` Bartlomiej Zolnierkiewicz
2020-01-29 14:15 ` Sergey Senozhatsky
2020-01-29 14:17 ` Sergey Senozhatsky
2020-01-29 14:40 ` Sergey Senozhatsky [this message]
2020-01-29 14:59 ` Dmitry Vyukov
2020-01-29 15:06 ` Dmitry Vyukov
2020-01-29 17:34 ` Tetsuo Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200129143754.GA15445@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=742991625abc@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--cc=syzkaller@googlegroups.com \
--cc=wangkefeng.wang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®