lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180923004113.GL4222@linux.ibm.com>
Date:   Sat, 22 Sep 2018 17:41:13 -0700
From:   "Paul E. McKenney" <paulmck@...ux.ibm.com>
To:     Joel Fernandes <joel@...lfernandes.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Jonathan Corbet <corbet@....net>,
        Josh Triplett <josh@...htriplett.org>,
        Lai Jiangshan <jiangshanlai@...il.com>,
        linux-doc@...r.kernel.org,
        Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
        Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH RFC] Documentation: RCU: Clarify comment about fanout

On Sat, Sep 22, 2018 at 07:38:05PM -0400, Joel Fernandes wrote:
> On Sat, Sep 22, 2018 at 9:46 AM Paul E. McKenney <paulmck@...ux.ibm.com> wrote:
> [...]
> > > I have a few more as well, I'll send them out soon.
> >
> > I do have on my list to update this document based on the changes in
> > -rcu, which among other things eliminate the rcu_dynticks structure
> > and  make it so there is only one rcu_state structure in a given
> > running system.
> >
> > If you are crazy enough to want to make the corresponding changes,
> > I would welcome the patches (and would be happy to help with editing,
> > grammar, and soforth.  The potential advantage to you is familiarlzation
> > with the new version of the code.
> >
> > This is not a small amount of work, so please give it some thought
> > before saying "yes".  (In contrast, I would of course understand and
> > respect an immediate "no".)
> 
> I thought about this and I'd be happy to do it as long as you don't
> mind me asking questions about parts I don't understand (which
> shouldn't be a problem from my past experience ;-)). I am spending
> time understanding the code anyway so I'd rather update the main
> documentation than my own notes for the benefit of everyone ;-) As you
> said, it'll help familiarization of the code. Btw I got rid of those
> extra rcu_state externs too, I'll send that patch out today and
> continue working on things next week...

If you continue to find and fix issues like your three most recent
patches, I really cannot complain about a few questions, now can I?  ;-)

So please keep both the patches and questions coming!

							Thanx, Paul

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ