Re: [BUG] invalid open call: O_CREAT or O_TMPFILE without mode

On Wed, Oct 12, 2016 at 11:32:16AM -0700, Andersen, John wrote:
 > Log attached. When I tried to fuzz devices in /dev. Hoping to fuzz an ioctl.
 > Trinity gets killed and displays the message seen in the subject.
 > 
 > 'invalid open call: O_CREAT or O_TMPFILE without mode'
 > 
 > I am running on Android which may have something / everything to do with this.
 > I just wanted to see if anyone has experienced this issue before. Otherwise
 > some pointers on where I might start looking to make a patch would be
 > appreciated.
 
I think this might be something that was fixed post 1.6.  Let me know if
it still happens with the version in git.

https://github.com/kernelslacker/trinity/commit/08bcce0b86046dc150d3100a77152dff7d19083c
should be the commit that fixed it.

I'll be doing a 1.7 tarball in a few weeks, there's been enough stuff
like this accumulated, along with all the new features.  Just need to
fix a handful of small problems.

	Dave