From: Johannes Thumshirn <jthumshirn@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>,
Vishal Verma <vishal.verma@intel.com>
Subject: Re: [PATCH] acpi/nfit: Fix bus command validation
Date: Wed, 20 Feb 2019 18:21:50 +0100 [thread overview]
Message-ID: <fcbf4a2c-a4c4-556e-f2dc-c22663997de5@suse.de> (raw)
In-Reply-To: <CAPcyv4hZXJbrLc9f3xsOTPs_RYVH9vhuxSxHj-4L56ZNi+ZRZg@mail.gmail.com>
On 20/02/2019 17:15, Dan Williams wrote:> I wouldn't be opposed to
syzkaller fuzzing the nvdimm-ioctl path.
As a heads up, I've started adding the ioctl() definitions to syzcaller.
Just so we don't duplicate any efforts.
Byte,
Johannes
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vishal Verma <vishal.verma@intel.com>,
stable <stable@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] acpi/nfit: Fix bus command validation
Date: Wed, 20 Feb 2019 18:21:50 +0100 [thread overview]
Message-ID: <fcbf4a2c-a4c4-556e-f2dc-c22663997de5@suse.de> (raw)
In-Reply-To: <CAPcyv4hZXJbrLc9f3xsOTPs_RYVH9vhuxSxHj-4L56ZNi+ZRZg@mail.gmail.com>
On 20/02/2019 17:15, Dan Williams wrote:> I wouldn't be opposed to
syzkaller fuzzing the nvdimm-ioctl path.
As a heads up, I've started adding the ioctl() definitions to syzcaller.
Just so we don't duplicate any efforts.
Byte,
Johannes
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2019-02-20 17:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 23:57 [PATCH] acpi/nfit: Fix bus command validation Dan Williams
2019-02-07 23:57 ` Dan Williams
2019-02-08 0:41 ` Verma, Vishal L
2019-02-08 0:41 ` Verma, Vishal L
[not found] ` <154958385172.3932544.193235520333886200.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2019-02-11 17:26 ` Sasha Levin
2019-02-20 1:56 ` Jeff Moyer
2019-02-20 1:56 ` Jeff Moyer
2019-02-20 2:58 ` Dan Williams
2019-02-20 2:58 ` Dan Williams
2019-02-20 8:29 ` Johannes Thumshirn
2019-02-20 8:29 ` Johannes Thumshirn
2019-02-20 16:15 ` Dan Williams
2019-02-20 16:15 ` Dan Williams
2019-02-20 17:21 ` Johannes Thumshirn [this message]
2019-02-20 17:21 ` Johannes Thumshirn
2019-02-21 13:28 ` Johannes Thumshirn
2019-02-21 13:28 ` Johannes Thumshirn
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=fcbf4a2c-a4c4-556e-f2dc-c22663997de5@suse.de \
--to=jthumshirn@suse.de \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=stable@vger.kernel.org \
--cc=vishal.verma@intel.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 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.