Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1370728
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260 |
| Date | 2016-04-04 18:10 +0200 |
| Message-ID | <rkfeG-5Fz-17@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <rhpNf-56p-1@gated-at.bofh.it> <rhXvz-3qM-1@gated-at.bofh.it> <rikLx-3iV-9@gated-at.bofh.it> <rioYO-6wN-13@gated-at.bofh.it> <rkeLD-57u-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Apr 04, 2016 at 05:31:40PM +0200, Sedat Dilek wrote:
> > +/* https://en.wikipedia.org/wiki/Xorshift#xorshift.2A */
> > +#define UINT64_C(x) x##ULL
> > +static inline u64 xorshift64star(u64 x)
> > +{
> > + x ^= x >> 12; // a
> > + x ^= x << 25; // b
> > + x ^= x >> 27; // c
> > + return x * UINT64_C(2685821657736338717);
> > +}
> Will you push that also to peterz/queue.git#locking/urgent?
Only after I've had a play and observed it making any difference; Dmitry
supposedly has a reproducer, but I've not yet had a moment to try.
> - Sedat -
>
> P.S.: "lockdep: print chain_key collision information" in your above
> tree differs from the upstream one.
I'll drop mine, I just hadn't moved to the very latestestest tip.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260 Sedat Dilek <sedat.dilek@gmail.com> - 2016-04-04 17:40 +0200 Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260 Peter Zijlstra <peterz@infradead.org> - 2016-04-04 18:10 +0200
csiph-web