public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Khazhy Kumykov <khazhy@google.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Gabriel Krisman Bertazi <krisman@collabora.com>,
	Hannes Reinecke <hare@suse.de>, Omar Sandoval <osandov@fb.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] eBFP for block devices
Date: Mon, 02 May 2022 16:34:02 -0400	[thread overview]
Message-ID: <yq1y1zjd6am.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CACGdZY+=Ugn0vd4+zsFoKwHp6f3Rv27wdssgvSoS_Onoi1yXUw@mail.gmail.com> (Khazhy Kumykov's message of "Mon, 2 May 2022 13:28:20 -0700")


Khazhy,

>> We've been working in this area too. It possible to write BPF filters to
>> protect block ranges using should_fail_bio().
>
> It'd be nice to have a "proper" api vs. ALLOW_ERROR_INJECTION, which
> feels more debug-y and has the drawback of
> CONFIG_FUNCTION_ERROR_INJECTION being all-or-nothing

I agree that it would be nice for this to be detached from error
injection.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2022-05-02 20:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 16:21 [LSF/MM/BPF TOPIC] eBFP for block devices Hannes Reinecke
2022-05-02 17:45 ` Gabriel Krisman Bertazi
2022-05-02 18:53   ` Martin K. Petersen
2022-05-02 20:28     ` Khazhy Kumykov
2022-05-02 20:34       ` Martin K. Petersen [this message]
2022-05-02 20:38         ` Hannes Reinecke
2022-05-02 20:47           ` Martin K. Petersen
2022-05-02 18:17 ` Omar Sandoval
2022-05-02 19:24   ` Hannes Reinecke
2023-01-29  3:20     ` Luis Chamberlain

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=yq1y1zjd6am.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=hare@suse.de \
    --cc=khazhy@google.com \
    --cc=krisman@collabora.com \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@fb.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