From: syzbot <bot+c0733f3aab92fc116dc1d10d8a25f5bf1f739eff@syzkaller.appspotmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: davem@davemloft.net, dvyukov@google.com, eric.dumazet@gmail.com,
jasowang@redhat.com, john.stultz@linaro.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
sboyd@codeaurora.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: Re: KASAN: use-after-free Write in detach_if_pending
Date: Mon, 30 Oct 2017 10:40:37 -0700 [thread overview]
Message-ID: <94eb2c189574effd6d055cc72269@google.com> (raw)
In-Reply-To: <CACT4Y+bRqQFNg-GL6Cd_gA6ZfJGz6Hb2Dhfjqp5fbvRWb+09Zg@mail.gmail.com>
> On Mon, Oct 30, 2017 at 6:30 PM, Eric Dumazet <eric.dumazet@gmail.com>
> wrote:
>> On Mon, 2017-10-30 at 18:06 +0100, Dmitry Vyukov wrote:
>>> Yes, but hashes in random trees also don't tell much. A tree can be
>>> rebased so the hash will be lost. It can be a tree unknown to the
>>> system. Even if we find the commit by hash, in order to match it
>>> against other trees we will have to use the title anyway (or are there
>>> better options?), so using hashes becomes pointless.
>> We do not send hashes on random trees, but official SHA1 in David Miller
>> trees. They will be the same SHA1 in official Linus Torvalds tree.
>> Really, you make our life more difficult by pretending that hashes are
>> not the proper way.
>> They are reasons we use Fixes: tags all over the places, they are unique
>> in Linus tree.
>> Since syzbot gives a SHA1 itself, it must be using a tree, right ?
>> So a SHA1 that is guaranteed to enter the same tree is correct.
>> Please fix your bot.
> They don't necessary enter the same tree (that's more of an exception
> than the rule). For bugs that we find in Linus tree, fixes enter usb,
> kvm, block, sound, linux-next and a bunch of other trees that I never
> heard of. At the very least we will need a git repo address + commit
> hash. But then for say linux-next hashes disappear. And mm which is
> not a git tree at all (no hashes).
> And still the hashes will need to be explicitly marked as fixes (with
> #syz fix or something else). So that would look like:
unknown command "fix"
> ##syz fix: git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> e7989f973ae1b90ec7c0b671c81f7f553affccbe
> which does not look much better than:
> ##syz fix: tun: do not arm flow_gc_timer in tun_flow_init()
> which also I think makes it easier for humans to ensure that they
> actually reference what they meant to reference (and maybe find the
> fix in other trees).
next prev parent reply other threads:[~2017-10-30 17:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 9:44 KASAN: use-after-free Write in detach_if_pending syzbot
2017-10-29 12:45 ` Thomas Gleixner
2017-10-29 13:01 ` Eric Dumazet
2017-10-30 15:48 ` Dmitry Vyukov
2017-10-30 16:36 ` Eric Dumazet
2017-10-30 17:06 ` Dmitry Vyukov
2017-10-30 17:30 ` Eric Dumazet
2017-10-30 17:40 ` Dmitry Vyukov
2017-10-30 17:40 ` syzbot [this message]
2017-10-30 17:47 ` Eric Dumazet
2017-10-30 17:52 ` Dmitry Vyukov
2017-10-30 18:27 ` Eric Dumazet
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=94eb2c189574effd6d055cc72269@google.com \
--to=bot+c0733f3aab92fc116dc1d10d8a25f5bf1f739eff@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jasowang@redhat.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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.