From: "Andersen, John" <john.s.andersen@intel.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: trinity@vger.kernel.org
Subject: Re: [BUG] invalid open call: O_CREAT or O_TMPFILE without mode
Date: Wed, 12 Oct 2016 13:04:29 -0700 [thread overview]
Message-ID: <20161012200429.GE32045@pdxjohnny> (raw)
In-Reply-To: <20161012192804.vc4jwo65dqdoewma@codemonkey.org.uk>
On Wed, Oct 12, 2016 at 03:28:04PM -0400, Dave Jones wrote:
> 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
>
Of course, I should have thought to pull from master. Thanks!
- John
prev parent reply other threads:[~2016-10-12 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 18:32 [BUG] invalid open call: O_CREAT or O_TMPFILE without mode Andersen, John
2016-10-12 19:28 ` Dave Jones
2016-10-12 20:04 ` Andersen, John [this message]
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=20161012200429.GE32045@pdxjohnny \
--to=john.s.andersen@intel.com \
--cc=davej@codemonkey.org.uk \
--cc=trinity@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).