From: "Arnd Bergmann" <arnd@arndb.de>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: "Christian Brauner" <brauner@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Jan Kara" <jack@suse.cz>, "Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] rust: miscdevice: add base miscdevice abstraction
Date: Wed, 02 Oct 2024 20:08:02 +0000 [thread overview]
Message-ID: <bdb276f3-154c-4e1a-95ef-15f9c2745da3@app.fastmail.com> (raw)
In-Reply-To: <2024100223-unwitting-girdle-92a5@gregkh>
On Wed, Oct 2, 2024, at 16:04, Greg Kroah-Hartman wrote:
> On Wed, Oct 02, 2024 at 03:45:08PM +0000, Arnd Bergmann wrote:
>> On Wed, Oct 2, 2024, at 14:23, Christian Brauner wrote:
>>
>> Here, the 64-bit 'old' has the same size as the 32-bit 'new',
>> so if we try to handle them in a shared native/compat ioctl
>> function, this needs an extra in_conmpat_syscall() check that
>> adds complexity and is easy to forget.
>
> Agreed, "extending" ioctls is considered a bad thing and it's just
> easier to create a new one. Or use some flags and reserved fields, if
> you remember to add them in the beginning...
>
> Anyway, this is all great, but for now, I'll take this series in my tree
> and we can add onto it from there. I'll dig up some sample code that
> uses this too, so that we make sure it works properly. Give me a few
> days to catch up before it lands in my trees...
Sounds good to me, it's clear we don't get a quick solution and
there is nothing stopping us from revisiting this after we have a
couple of drivers using ioctl.
Arnd
next prev parent reply other threads:[~2024-10-02 20:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 8:22 [PATCH v2 0/2] Miscdevices in Rust Alice Ryhl
2024-10-01 8:22 ` [PATCH v2 1/2] rust: types: add Opaque::try_ffi_init Alice Ryhl
2024-10-01 8:46 ` Benno Lossin
2024-10-25 4:10 ` Trevor Gross
2024-10-25 7:57 ` Alice Ryhl
2024-10-01 8:22 ` [PATCH v2 2/2] rust: miscdevice: add base miscdevice abstraction Alice Ryhl
2024-10-01 8:53 ` Dirk Behme
2024-10-01 9:13 ` Alice Ryhl
2024-10-01 11:28 ` Alice Ryhl
2024-10-02 12:48 ` Arnd Bergmann
2024-10-02 12:58 ` Alice Ryhl
2024-10-02 13:24 ` Arnd Bergmann
2024-10-02 13:31 ` Alice Ryhl
2024-10-02 13:57 ` Arnd Bergmann
2024-10-02 14:23 ` Alice Ryhl
2024-10-02 15:31 ` Arnd Bergmann
2024-10-02 13:24 ` Christian Brauner
2024-10-02 13:36 ` Alice Ryhl
2024-10-02 14:23 ` Christian Brauner
2024-10-02 15:45 ` Arnd Bergmann
2024-10-02 16:04 ` Greg Kroah-Hartman
2024-10-02 20:08 ` Arnd Bergmann [this message]
2024-10-03 8:19 ` Christian Brauner
2024-10-03 8:09 ` Christian Brauner
2024-10-02 13:31 ` Christian Brauner
2024-10-02 14:06 ` Christian Brauner
2024-10-02 14:24 ` Alice Ryhl
2024-10-03 8:33 ` Christian Brauner
2024-10-21 10:34 ` Miguel Ojeda
2024-10-22 13:15 ` Alice Ryhl
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=bdb276f3-154c-4e1a-95ef-15f9c2745da3@app.fastmail.com \
--to=arnd@arndb.de \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=viro@zeniv.linux.org.uk \
/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).