From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Open tasks?
Date: Thu, 30 Jan 2020 10:00:09 +0000 [thread overview]
Message-ID: <20200130100009.GD1778@kadam> (raw)
In-Reply-To: <CAHM57JSf8XXOKzyjBWD3m7PPUaEC7Oa_XYyOjbcEfJj5Swxu7Q@mail.gmail.com>
On Mon, Jan 20, 2020 at 08:36:32PM -0800, Raymond Deng wrote:
> Hi, are there open tasks for reasonably new people to do? Thanks.
The new hotest idea is to sign up for te syzbot mailing list and fix
bugs.
For example:
https://syzkaller.appspot.com/bug?extidÃ7a14770d51a085a520
It has a c reproducer. It has been bisected but if it's a race
condition, the git bisection could be suspect. It affects v5.5-rc7
(It's in the dmesg, you need the version information for the lines to
match up).
My first thought was that it is an integer overflow but I can't see how
that would be possible. Smatch said it was possible, but Smatch assumed
that we had set vc->vc_cols to an invalid number before the start.
Btw, using the Smatch `smdb.py where vc_cols` command is super helpful
for debugging these bugs.
Then my next thought was that it is a race condition but we're always
holding the console_lock() so I can't see how that works either...
Again for these things `smdb.py` really helps for examining the callers.
I'm working on recording when the caller is holding a lock but it's a
bit complicated and I'm not ready to push that code yet.
It's a mystery.
regards,
dan carpenter
prev parent reply other threads:[~2020-01-30 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 4:34 Open tasks? Raymond Deng
2020-01-21 4:36 ` Raymond Deng
2020-01-30 10:00 ` Dan Carpenter [this message]
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=20200130100009.GD1778@kadam \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.