Posts
48
Following
40
Followers
133
paulmckrcu

Paul E. McKenney

Reply to @sima@chaos.social
@sima @brauner @jann @vbabka RCU is benign? May I please get that in writing? ;-)
1
0
2
paulmckrcu

Paul E. McKenney

Reply to
@ljs @jann That does sound like it might require unusually disciplined users! But what is it currently used for?
0
0
2
paulmckrcu

Paul E. McKenney

Reply to
@ljs It is amazing how destructive unanticipated use cases can be. Destructive, but necessary...
0
0
2
paulmckrcu

Paul E. McKenney

Reply to @brauner@mastodon.social
@brauner @jann It has been a very long time since I have seen a local filesystem operation take very long, so no argument here!
0
0
1
paulmckrcu

Paul E. McKenney

Reply to @brauner@mastodon.social
@brauner @jann Use AI to find the xfstest of interest? (OK, OK, I will get my coat...)
0
0
2
paulmckrcu

Paul E. McKenney

Reply to @jann@infosec.exchange
@jann @brauner As always, the big question is "what would have detected the bug earlier and more deterministically?" Finding the extreme corner cases is inherently hard, because that is exactly why we call them "extreme".
1
0
2
paulmckrcu

Paul E. McKenney

Reply to @jann@infosec.exchange
@jann @brauner Or to recover from the next timeout being unduly delayed, for that matter. That said, in my experience, most timeout handlers unconditionally do their work. On the other hand, I could easily believe that unconditional timeout handlers are much less likely to come to your attention. ;-)
0
0
2
paulmckrcu

Paul E. McKenney

Reply to @brauner@mastodon.social
@brauner @jann Or a way to fuzz the timers. Though some would argue that the kernel as it is does a pretty good job of this sort of fuzzing...
0
0
2
paulmckrcu

Paul E. McKenney

Reply to @brauner@mastodon.social
@brauner @jann To be fair, that does fall into the first of Jann's valid use cases: "a remote system is not responding, drop the connection and maybe connect again later".
0
0
0
paulmckrcu

Paul E. McKenney

Reply to @brauner@mastodon.social
@brauner @jann Interruptible/killable sleeping locks can be used for latency reduction for the poor user who didn't realize how long things might take.

Of course, there just might a few Interruptible/killable sleep-lock failure paths in need of better testing... ;-)
1
0
3
paulmckrcu

Paul E. McKenney

Reply to @jann@infosec.exchange
@jann Another use case is periodic polling. Yet another is dealing with latency constraints, for example, compute it the hard and accurate way, but if that takes too long, compute it more quickly and less accurately. Another involves needing to do things that are not permitted in a restrictive context (e.g., interrupt handler), though things like irq work are better on architectures providing this.

All that aside, yes, I have seen timeouts used in cases where investing a little more thought might have provided a better solution. Then again, the same is true of pretty much all other facilities provided by the Linux kernel. ;-)
0
0
2
paulmckrcu

Paul E. McKenney

Reply to @jann@infosec.exchange
@jann Timeouts. Can't live with them, can't live without them. ;-)
1
0
4
paulmckrcu

Paul E. McKenney

Slides from this weekend's Oregon State University Beaver BarCamp. Unusual topic, but a request. Fun session, good interaction.

https://drive.google.com/file/d/1-0si8ZhUTE-SA94g_mrBvJuVL1GoQrZ9/view?usp=sharing
0
4
6
paulmckrcu

Paul E. McKenney

Reply to @rw
@rw Boy does that poster bring back memories! Thank you for that! ;-)
1
0
1
paulmckrcu

Paul E. McKenney

Reply to @monsieuricon
@monsieuricon There is always Breve Court, a short street in Las Vegas, otherwise known as Breve Ct.
0
0
0
paulmckrcu

Paul E. McKenney

Reply to @jfbastien@mastodon.social
@jfbastien @cliffle @luna All of them!!! ;-)
0
0
1
paulmckrcu

Paul E. McKenney

It is my honor to be designated as Godfather of the 2025 edition of Kernel Recipes. The conference organizers made it quite clear that they would like some focus on increasing the speaking skills of the presenters. This blog series is a first step in that direction: https://people.kernel.org/paulmck/kernel-recipes-2025
0
16
20
paulmckrcu

Paul E. McKenney

Reply to @bagder@mastodon.social
@bagder The ones that this is said to be responding to? https://www.linuxfoundation.org/blog/navigating-global-regulations-and-open-source-us-ofac-sanctions
0
0
0
paulmckrcu

Paul E. McKenney

Reply to @bagder@mastodon.social
@bagder Dealing with the arising geopolitical threats to open source?
1
0
0
paulmckrcu

Paul E. McKenney

Reply to @penguin42@mastodon.org.uk
@penguin42 I will get on that! ;-)
0
0
0
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: