From: Steve French <smfrench@gmail.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Mysterious fs ioctl
Date: Mon, 21 Oct 2019 20:22:48 -0500 [thread overview]
Message-ID: <CAH2r5mtTodYZ9JcAnkEaK6Narc_tj4-d9d5=WAYDSf-qcFJFMg@mail.gmail.com> (raw)
Trying to track down this failing ioctl (on a file opened O_DIRECT):
strace showed:
ioctl(4, _IOC(_IOC_WRITE, 0x95, 0x2, 0x4), 0x7ffe5b491664) = -1
ENOTTY (Inappropriate ioctl for device)
I could find ioctls for 0x94 but not 0x95 in kernel source ... any
idea what ioctl
_IOC_WRITE, 0x95, 0x2, 0x4)
is?
Wanted to make sure cifs.ko wasn't missing handling some important
ioctl for O_DIRECT workloads ...
--
Thanks,
Steve
reply other threads:[~2019-10-22 1:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAH2r5mtTodYZ9JcAnkEaK6Narc_tj4-d9d5=WAYDSf-qcFJFMg@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@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 NNTP newsgroup(s).