Re: [tip:x86/urgent] x86/mm/kasan: Don't use vmemmap_populate() to initialize shadow

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

 



On Tue, Nov 21, 2017 at 11:46 PM, tip-bot for Andrey Ryabinin
<tipbot@xxxxxxxxx> wrote:
> Commit-ID:  f68d62a56708b0c19dca7a998f408510f2fbc3a8
> Gitweb:     https://git.kernel.org/tip/f68d62a56708b0c19dca7a998f408510f2fbc3a8
> Author:     Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
> AuthorDate: Wed, 15 Nov 2017 17:36:35 -0800
> Committer:  Ingo Molnar <mingo@xxxxxxxxxx>
> CommitDate: Wed, 22 Nov 2017 07:18:35 +0100
>
> x86/mm/kasan: Don't use vmemmap_populate() to initialize shadow
>
> [ Note, this commit is a cherry-picked version of:
>
>     d17a1d97dc20: ("x86/mm/kasan: don't use vmemmap_populate() to initialize shadow")
>
>   ... for easier x86 entry code testing and back-porting. ]

I'm confused.  Isn't this patch already in Linus' tree, merged in (I
think) 7c225c69f86c934e3be9be63ecde754e286838d7?
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Stable Commits]     [Linux Stable Kernel]     [Linux Kernel]     [Linux USB Devel]     [Linux Video &Media]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux