linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marco Elver <elver@google.com>
To: Shaobo Huang <huangshaobo6@huawei.com>
Cc: akpm@linux-foundation.org, chenzefeng2@huawei.com,
	dvyukov@google.com,  glider@google.com,
	kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
	 linux-mm@kvack.org, nixiaoming@huawei.com, wangbing6@huawei.com,
	 wangfangpeng1@huawei.com, young.liuyang@huawei.com,
	zengweilin@huawei.com,  zhongjubin@huawei.com
Subject: Re: [PATCH] kfence: check kfence canary in panic and reboot
Date: Sun, 24 Apr 2022 11:51:34 +0200	[thread overview]
Message-ID: <CANpmjNOOE8z_YYbJXsv=hxBhvCHyWhYapA8VKgnk2bHAtL6=8Q@mail.gmail.com> (raw)
In-Reply-To: <20220424081049.57928-1-huangshaobo6@huawei.com>

On Sun, 24 Apr 2022 at 10:10, Shaobo Huang <huangshaobo6@huawei.com> wrote:
>
> On Thu, 21 Apr 2022 15:28:45 +0200, Marco Elver <elver@google.com> wrote:
> > On Thu, 21 Apr 2022 at 15:06, Alexander Potapenko <glider@google.com> wrote:
> > [...]
> > > This report will denote that in a system that could have been running for days a particular skbuff was corrupted by some unknown task at some unknown point in time.
> > > How do we figure out what exactly caused this corruption?
> > >
> > > When we deploy KFENCE at scale, it is rarely possible for the kernel developer to get access to the host that reported the bug and try to reproduce it.
> > > With that in mind, the report (plus the kernel source) must contain all the necessary information to address the bug, otherwise reporting it will result in wasting the developer's time.
> > > Moreover, if we report such bugs too often, our tool loses the credit, which is hard to regain.
> >
> > I second this - in particular we'll want this off in fuzzers etc.,
> > because it'll just generate reports that nobody can use to debug an
> > issue. I do see the value in this in potentially narrowing the cause
> > of a panic, but that information is likely not enough to fully
> > diagnose the root cause of the panic - it might however prompt to
> > re-run with KASAN, or check if memory DIMMs are faulty etc.
> >
> > We can still have this feature, but I suggest to make it
> > off-by-default, and only enable via a boot param. I'd call it
> > 'kfence.check_on_panic'. For your setup, you can then use it to enable
> > where you see fit.
>
> Can I implement your suggestion into the second patch and add the "Suggested-by: Marco Elver <elver@google.com>" tag to it?

I don't think it's necessary, after all the overall patch is still
your idea - you're just using our review feedback to improve it. In
the change-log (after ---) you can of course mention that, but it'll
be stripped upon applying.

Thanks,
-- Marco


      reply	other threads:[~2022-04-24  9:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 10:49 Shaobo Huang
2022-04-20 11:11 ` Marco Elver
2022-04-21  8:37   ` Shaobo Huang
2022-04-21  8:50     ` Marco Elver
2022-04-21  9:12       ` Shaobo Huang
2022-04-21 10:03 ` Alexander Potapenko
2022-04-21 12:10   ` Shaobo Huang
2022-04-21 13:06     ` Alexander Potapenko
2022-04-21 13:28       ` Marco Elver
2022-04-21 13:46         ` Shaobo Huang
2022-04-24  8:10         ` Shaobo Huang
2022-04-24  9:51           ` Marco Elver [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='CANpmjNOOE8z_YYbJXsv=hxBhvCHyWhYapA8VKgnk2bHAtL6=8Q@mail.gmail.com' \
    --to=elver@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=chenzefeng2@huawei.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=huangshaobo6@huawei.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nixiaoming@huawei.com \
    --cc=wangbing6@huawei.com \
    --cc=wangfangpeng1@huawei.com \
    --cc=young.liuyang@huawei.com \
    --cc=zengweilin@huawei.com \
    --cc=zhongjubin@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