public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1][CLEANUP] x86: use already defined macros instead of hard-coded values
Date: Thu, 5 Mar 2015 19:17:55 +0100	[thread overview]
Message-ID: <20150305181755.GL3915@pd.tnic> (raw)
In-Reply-To: <CANCZXo5t9f+O2r9AT9ssqXuQyHvb4aC7iacKAvAbPMao2rH5ag@mail.gmail.com>

On Fri, Mar 06, 2015 at 12:12:09AM +0600, Alexander Kuleshov wrote:
> Ok, i looked on it with gdb, and X86_FEATURE_NX is not correct here.
> It's a bug number one.

Yes, X86_FEATURE_NX is not the same bit type as the bits you have in
%edi.

> And L3_START_KERNEL*8 + 1, must be L3_START_KERNEL*8 + 8, as we works
> with page entries
> or i'm wrong here?

Yes.

And look at the code after you've changed it. Do you think someone
looking at it a couple of months from now will know what

L3_START_KERNEL*8 + 8

or 

(L3_START_KERNEL + 1)*8

means?

So having 510 and 511 to mean the last two page table entries is much
more understandable.

Like I told you a couple of days ago, please don't waste your time with
stuff which already works and there are no problems with and go look for
real bugs. Believe me, there are plenty out there.

> Anyway, thanks for education:)

No problem.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

      reply	other threads:[~2015-03-05 18:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 13:30 [PATCH v1][CLEANUP] x86: use already defined macros instead of hard-coded values Alexander Kuleshov
2015-03-05 17:22 ` Borislav Petkov
2015-03-05 17:52   ` Steven Rostedt
2015-03-05 18:01     ` Steven Rostedt
2015-03-05 18:12   ` Alexander Kuleshov
2015-03-05 18:17     ` Borislav Petkov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150305181755.GL3915@pd.tnic \
    --to=bp@alien8.de \
    --cc=kuleshovmail@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox