linux-kernel - Re: [PATCH] rcu: don't include <linux/ktime.h> in rcutiny.h

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20190822140042.GZ28441@linux.ibm.com>
Date:   Thu, 22 Aug 2019 07:00:42 -0700
From:   "Paul E. McKenney" <paulmck@...ux.ibm.com>
To:     Christoph Hellwig <hch@....de>
Cc:     josh@...htriplett.org, rcu@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rcu: don't include <linux/ktime.h> in rcutiny.h

On Thu, Aug 22, 2019 at 05:48:41AM +0200, Christoph Hellwig wrote:
> On Wed, Aug 21, 2019 at 08:02:00PM -0700, Paul E. McKenney wrote:
> > On Thu, Aug 22, 2019 at 10:53:43AM +0900, Christoph Hellwig wrote:
> > > The kbuild reported a built failure due to a header loop when RCUTINY is
> > > enabled with my pending riscv-nommu port.  Switch rcutiny.h to only
> > > include the minimal required header to get HZ instead.
> > > 
> > > Signed-off-by: Christoph Hellwig <hch@....de>
> > 
> > Queued for review and testing, thank you!
> > 
> > Do you need this in v5.4?  My normal workflow would put it into v5.5.
> 
> I hope the riscv-nommu coe gets merges for 5.4, so if we could queue
> it up for that I'd appreciate it.

OK, it did pass rcutorture's various !SMP scenarios, so this seems
plausible.

I am sending my main pull request today, but will also put this patch
where 0day and -next can see it.  If it does OK with that and with
additional review/testing for a few days, I will send a second pull
request with that patch some time next week.

							Thanx, Paul