rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Miguel Ojeda <ojeda@kernel.org>, John Stultz <jstultz@google.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Alex Gaynor <alex.gaynor@gmail.com>,
	Wedson Almeida Filho <wedsonaf@gmail.com>,
	Gary Guo <gary@garyguo.net>,
	bjorn3_gh@protonmail.com, Benno Lossin <benno.lossin@proton.me>,
	Andreas Hindborg <a.hindborg@samsung.com>,
	Alice Ryhl <aliceryhl@google.com>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH 2/2] rust: time: Use wrapping_sub() for Ktime::sub()
Date: Mon, 13 May 2024 07:06:19 -0700	[thread overview]
Message-ID: <ZkIeW_NgXFYsAx5M@boqun-archlinux> (raw)
In-Reply-To: <87cypvnpwn.ffs@tglx>

On Thu, May 09, 2024 at 02:14:16PM +0200, Thomas Gleixner wrote:
> On Tue, Apr 23 2024 at 14:11, Boqun Feng wrote:
> > On Thu, Apr 11, 2024 at 04:08:01PM -0700, Boqun Feng wrote:
> >> Currently since Rust code is compiled with "-Coverflow-checks=y", so a
> >> normal substraction may be compiled as an overflow checking and panic
> >> if overflow happens:
> >> 
> >>         subq    %rsi, %rdi
> >>         jo      .LBB0_2
> >>         movq    %rdi, %rax
> >>         retq
> >> .LBB0_2:
> >>         pushq   %rax
> >>         leaq    str.0(%rip), %rdi
> >>         leaq    .L__unnamed_1(%rip), %rdx
> >>         movl    $33, %esi
> >>         callq   *core::panicking::panic::h59297120e85ea178@GOTPCREL(%rip)
> >> 
> >> although overflow detection is nice to have, however this makes
> >> `Ktime::sub()` behave differently than `ktime_sub()`, moreover it's not
> >> clear that the overflow checking is helpful, since for example, the
> >> current binder usage[1] doesn't have the checking.
> >
> > Ping. Thomas, John and Stepthen. Could you take a look at this, and the
> > discussion between Miguel and me? The key question is the behavior when
> > ktime_sub() hits a overflow, I think. Thanks!
> 
> In principle ktime_sub() should not overflow for regular use cases.
> 
> If the binder example overflows the substraction, then something is
> seriously wrong. Though in that case as it's only for debug purposes
> panicing would be totally counter productive. A warning might be
> appropriate though.
> 

Thanks! Looks to me, a reasonable implementation would be calling
`overflowing_sub`[1] and print a warning if overflow happens:

	<in the implementation of Sub trait of Ktime>

	let (ret, overflow) = self.inner.overflowing_sub(other.inner);

	if overflow {
		pr_err!("Overflow on Ktime: {} - {}\n", self.inner, other.inner);
	}

	return ret;

I will use this as a new version for more reviews.

[1]: https://doc.rust-lang.org/std/primitive.i64.html#method.overflowing_sub

Regards,
Boqun

> Thanks,
> 
>         tglx
> 
> 

  reply	other threads:[~2024-05-13 14:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 23:07 [PATCH 0/2] rust: time related cleanup Boqun Feng
2024-04-11 23:08 ` [PATCH 1/2] rust: time: doc: Add missing C header links Boqun Feng
2024-04-12  7:15   ` Miguel Ojeda
2024-04-12 11:04   ` Alice Ryhl
2024-04-11 23:08 ` [PATCH 2/2] rust: time: Use wrapping_sub() for Ktime::sub() Boqun Feng
2024-04-12  7:14   ` Miguel Ojeda
2024-04-12  7:43     ` Philipp Stanner
2024-04-12  7:58       ` Miguel Ojeda
2024-04-15 17:08         ` Kees Cook
2024-04-12 13:34     ` Boqun Feng
2024-04-12 14:41       ` Miguel Ojeda
2024-04-13  1:30         ` Boqun Feng
2024-04-13  2:16           ` Miguel Ojeda
2024-04-12  8:36   ` Alice Ryhl
2024-04-12 13:18     ` Boqun Feng
2024-04-12 13:51       ` Alice Ryhl
2024-04-25  9:00         ` Andreas Hindborg
2024-04-25 14:28           ` Boqun Feng
2024-04-23 21:11   ` Boqun Feng
2024-04-23 23:37     ` Kees Cook
2024-04-24 10:21       ` Miguel Ojeda
2024-05-09 12:14     ` Thomas Gleixner
2024-05-13 14:06       ` Boqun Feng [this message]
2024-05-13 15:04       ` Miguel Ojeda
2024-05-14 13:12         ` Boqun Feng
2024-05-14 14:21           ` Miguel Ojeda

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=ZkIeW_NgXFYsAx5M@boqun-archlinux \
    --to=boqun.feng@gmail.com \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=gary@garyguo.net \
    --cc=jstultz@google.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wedsonaf@gmail.com \
    /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).