On Wed, Feb 20, 2019 at 12:30 AM Johannes Thumshirn <jthumshirn(a)suse.de> wrote:
On 20/02/2019 03:58, Dan Williams wrote:
>> Tricky code path, eh?
> ioctl path, number one source of bugs / thrash in this subsystem. 2nd
> place, ARS.
Possibly unpopular idea, but should we maybe teach trinity/syzcaller
about these ioctl()s?
Better we find the bugs in a QA like environment than in the filed, I guess?
I wouldn't be opposed to syzkaller fuzzing the nvdimm-ioctl path.