linux-kernel - Re: [PATCH 4/4] x86: Replace xxx_pda() operations with x86_xx

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <484E98C4.4040308@sgi.com>
Date:	Tue, 10 Jun 2008 08:07:48 -0700
From:	Mike Travis <travis@....com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Christoph Lameter <clameter@....com>,
	David Miller <davem@...emloft.net>,
	Eric Dumazet <dada1@...mosbay.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] x86: Replace xxx_pda() operations with	x86_xx_percpu().

Ingo Molnar wrote:
> * Mike Travis <travis@....com> wrote:
> 
>> Ingo Molnar wrote:
>>> * Mike Travis <travis@....com> wrote:
>>>
>>>>   * It is now possible to use percpu operations for pda access
>>>>     since the pda is in the percpu area. Drop the pda operations.
>>> FYI, this one didnt build with the attached config.
>>>
>>> 	Ingo
>>>
>> Hi Ingo,
>>
>> Can you send me the output from the build?  It builds fine on my 
>> machine (a few warnings).  The silentoldconfig made these changes to 
>> the .config file.  (I did a git-remote update and reapplied my changes 
>> before building.)
> 
> dont have the log anymore, but i had to revert 3/4 due to the boot 
> crash, could there be a dependency of 4/4 on 3/4?
> 
> the first two patches look fine and survived -tip testing.
> 
> 	Ingo

Thanks Ingo.  I'm narrowing down the reboot problem by pulling config
items out.  I managed to get it to boot but now am trying to understand
how those config options are causing the problem.

Btw, it does not panic/reboot on linux-next with the original config.
Perhaps I should try and bisect to an earlier patch to see what that
reveals?

Thanks,
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/