linux-kernel - strex instrucion question in v6_early

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <28c262360801240047h2a2d31b5o477d7537224df7f2@mail.gmail.com>
Date:	Thu, 24 Jan 2008 17:47:53 +0900
From:	"minchan kim" <minchan.kim@...il.com>
To:	catalin.marinas@....com
Cc:	linux-kernel@...r.kernel.org
Subject: strex instrucion question in v6_early_abort

Hi catalin,

Now I am trying to understand your patch in linux kernel.

  .align  5
ENTRY(v6_early_abort)
#ifdef CONFIG_CPU_32v6K
  clrex
#else
  strex r0, r1, [sp]      @ Clear the exclusive monitor
<====================== This
#endif
  mrc p15, 0, r1, c5, c0, 0   @ get FSR
  mrc p15, 0, r0, c6, c0, 0   @ get FAR

I think that you insert just ""dummy strex"" for preventing
unpredicatable state of exclusive monitor. Is right?
If it is right, Why do you use r1, [sp] in all of registers ? Is there
any issue ?


-- 
Kinds regards,
barrios
--
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/