Re: sparc64: hang from BUG: Bad page state, on older CPU & compiler

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Meelis Roos <mroos@xxxxxxxx>
Subject: Re: sparc64: hang from BUG: Bad page state, on older CPU & compiler
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Sun, 18 Aug 2019 00:01:37 -0700
Cc: Sparc kernel list <sparclinux@xxxxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Dave Miller <davem@xxxxxxxxxxxxx>
In-reply-to: <d2a51bfb-84e4-3ce7-ac48-7200b3a8d722@linux.ee>
References: <d2a51bfb-84e4-3ce7-ac48-7200b3a8d722@linux.ee>
User-agent: Mutt/1.11.4 (2019-03-13)

I think for now we'll simply have to disable HAVE_FAST_GUP for sparc,
until someone who really knows low-level sparc page table handling
finds some time to audit the generic fast gup code and arch hooks.

Follow-Ups:
- Re: sparc64: hang from BUG: Bad page state, on older CPU & compiler
  - From: David Miller

References:
- sparc64: hang from BUG: Bad page state, on older CPU & compiler
  - From: Meelis Roos

Prev by Date: Re: [PATCH 14/26] asm-generic: don't provide __ioremap
Next by Date: Re: sparc64: hang from BUG: Bad page state, on older CPU & compiler
Previous by thread: sparc64: hang from BUG: Bad page state, on older CPU & compiler
Next by thread: Re: sparc64: hang from BUG: Bad page state, on older CPU & compiler
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Development] [DCCP] [Linux ARM Development] [Linux] [Photo] [Yosemite Help] [Linux ARM Kernel] [Linux SCSI] [Linux x86_64] [Linux Hams]

Powered by Linux