From: Kees Cook <keescook@chromium.org>
To: Kevin Mitchell <kevmitch@arista.com>
Cc: linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Akinobu Mita <akinobu.mita@gmail.com>,
Jonathan Corbet <corbet@lwn.net>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hannes Reinecke <hare@suse.de>,
Bart Van Assche <bvanassche@acm.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] lkdtm: remove IDE_CORE_CP crashpoint
Date: Wed, 18 Aug 2021 20:10:59 -0700 [thread overview]
Message-ID: <202108182010.C7278F4FAA@keescook> (raw)
In-Reply-To: <20210819022940.561875-3-kevmitch@arista.com>
On Wed, Aug 18, 2021 at 07:29:40PM -0700, Kevin Mitchell wrote:
> With the removal of the legacy IDE driver in kb7fb14d3ac63 ("ide: remove
> the legacy ide driver"), this crashpoint no longer points to a valid
> function.
>
> Signed-off-by: Kevin Mitchell <kevmitch@arista.com>
Hah, whoops. Yes. :)
Acked-by: Kees Cook <keescook@chromium.org>
Thanks!
-Kees
> ---
> Documentation/fault-injection/provoke-crashes.rst | 3 +--
> drivers/misc/lkdtm/core.c | 1 -
> 2 files changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/Documentation/fault-injection/provoke-crashes.rst b/Documentation/fault-injection/provoke-crashes.rst
> index 18de17354206..3abe84225613 100644
> --- a/Documentation/fault-injection/provoke-crashes.rst
> +++ b/Documentation/fault-injection/provoke-crashes.rst
> @@ -29,8 +29,7 @@ recur_count
> cpoint_name
> Where in the kernel to trigger the action. It can be
> one of INT_HARDWARE_ENTRY, INT_HW_IRQ_EN, INT_TASKLET_ENTRY,
> - FS_DEVRW, MEM_SWAPOUT, TIMERADD, SCSI_QUEUE_RQ,
> - IDE_CORE_CP, or DIRECT
> + FS_DEVRW, MEM_SWAPOUT, TIMERADD, SCSI_QUEUE_RQ, or DIRECT.
>
> cpoint_type
> Indicates the action to be taken on hitting the crash point.
> diff --git a/drivers/misc/lkdtm/core.c b/drivers/misc/lkdtm/core.c
> index 016cb0b150fc..e50e7bfc4674 100644
> --- a/drivers/misc/lkdtm/core.c
> +++ b/drivers/misc/lkdtm/core.c
> @@ -83,7 +83,6 @@ static struct crashpoint crashpoints[] = {
> CRASHPOINT("MEM_SWAPOUT", "shrink_inactive_list"),
> CRASHPOINT("TIMERADD", "hrtimer_start"),
> CRASHPOINT("SCSI_QUEUE_RQ", "scsi_queue_rq"),
> - CRASHPOINT("IDE_CORE_CP", "generic_ide_ioctl"),
> #endif
> };
>
> --
> 2.32.0
>
--
Kees Cook
next prev parent reply other threads:[~2021-08-19 3:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 2:29 [PATCH v2 0/2] lkdtm: update block layer crashpoints Kevin Mitchell
2021-08-19 2:29 ` [PATCH v2 1/2] lkdtm: replace SCSI_DISPATCH_CMD with SCSI_QUEUE_RQ Kevin Mitchell
2021-08-19 3:10 ` Kees Cook
2021-08-19 6:53 ` Christoph Hellwig
2021-08-19 2:29 ` [PATCH v2 2/2] lkdtm: remove IDE_CORE_CP crashpoint Kevin Mitchell
2021-08-19 3:10 ` Kees Cook [this message]
2021-08-19 6:53 ` Christoph Hellwig
2021-08-19 7:09 ` [PATCH v2 0/2] lkdtm: update block layer crashpoints Kees Cook
2021-08-24 3:10 ` Martin K. Petersen
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=202108182010.C7278F4FAA@keescook \
--to=keescook@chromium.org \
--cc=akinobu.mita@gmail.com \
--cc=arnd@arndb.de \
--cc=bvanassche@acm.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=kevmitch@arista.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).