All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Sitnicki <jakub@cloudflare.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@cloudflare.com,
	linux-kbuild@vger.kernel.org, x86@kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Wei Yongjun <weiyongjun1@huawei.com>
Subject: Re: [PATCH] fault-inject: Enable stacktrace filter for x86-64
Date: Mon, 14 Nov 2022 10:56:26 +0100	[thread overview]
Message-ID: <87a64too2r.fsf@cloudflare.com> (raw)
In-Reply-To: <CAC5umyhw=V1O_cC+Q4=XSye7htJ1aSAhMmbqSe7TngsohhuQ6w@mail.gmail.com>

On Sat, Nov 12, 2022 at 01:41 AM +09, Akinobu Mita wrote:
> 2022年11月10日(木) 20:30 Jakub Sitnicki <jakub@cloudflare.com>:
>>
>> Stacktrace filtering for fault injection has been disabled on x86-64 since
>> 2007 due to the lack of a DWARF unwinder. See commit 6d690dcac92a ("fault
>> injection: disable stacktrace filter for x86-64").
>>
>> In 2017, the ORC unwider, an alternative to DWARF unwinder has been added
>> in commit ee9f8fce9964 ("x86/unwind: Add the ORC unwinder").
>>
>> We can now re-enable the stacktrace filter for x86-64.
>
> The same change by Wei Yongjun is already in the linux-next via -mm tree.
>
> But thank you for the good explanation.

Thanks for letting me know. Will check linux-next next time.

Please ignore my patch. Sorry for the noise.

      reply	other threads:[~2022-11-14 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 11:30 [PATCH] fault-inject: Enable stacktrace filter for x86-64 Jakub Sitnicki
2022-11-11 16:41 ` Akinobu Mita
2022-11-14  9:56   ` Jakub Sitnicki [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=87a64too2r.fsf@cloudflare.com \
    --to=jakub@cloudflare.com \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kernel-team@cloudflare.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=weiyongjun1@huawei.com \
    --cc=x86@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.