linux-kernel - Re: Back porting preemption timer patches from 4.13 to 4.9 RT kernel

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

Message-ID: <FC282DC1-A0B0-4127-824E-0AD3E8E62DDA@viasat.com>
Date:   Fri, 26 Jan 2018 19:10:22 +0000
From:   "Arisetty, Chakravarthy" <Chakravarthy.Arisetty@...sat.com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Wanpeng Li <wanpeng.li@...mail.com>
CC:     Paolo Bonzini <pbonzini@...hat.com>,
        Radim Krčmář <rkrcmar@...hat.com>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        "x86@...nel.org" <x86@...nel.org>,
        "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Uberoy, Pawan" <Pawan.Uberoy@...sat.com>,
        "Mani, Somnath" <Somnath.Mani@...sat.com>,
        "Rich, Dennis" <Dennis.Rich@...sat.com>
Subject: Re: Back porting preemption timer patches from 4.13 to 4.9 RT kernel



On 1/25/18, 10:34 PM, "Thomas Gleixner" <tglx@...utronix.de> wrote:

    On Fri, 26 Jan 2018, Wanpeng Li wrote:
    
    > > > >Folks, can you please stop this corporate email style nonsense?
    
    > On 1/26/18 12:55 AM, Arisetty, Chakravarthy wrote:
    > >> IIRC，the race which KVM: LAPIC: Fix reentrancy issues with preempt notifiers<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.kernel.org_pub_scm_linux_kernel_git_stable_linux-2Dstable.git_commit_arch_x86_kvm_lapic.c-3Fh-3Dlinux-2D4.13.y-26id-3D1d518c6820daf4e00d29adfba980aee05f605f0f&d=DwMGaQ&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=Ffjvk4Y8xEf_-aLPhDRUD2drOoDsZ0R_uiCBYAvmwAY&m=HxxYRqfeH8SOgZuryI2hIvUXHNgkHkYSOXflazJS-h8&s=Ucf0XMULwrmlqxf5Q-IEoiZVHM1hkEL2Xz5RRCqUmQA&e=>  tries to fix is exposed by refactor restart_apic_timer patchset. If you don't care the latency which https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2017_6_29_604&d=DwIDaQ&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=Ffjvk4Y8xEf_-aLPhDRUD2drOoDsZ0R_uiCBYAvmwAY&m=EBYCZh6wt6GGpGerm3mGVpYx2BbZ1oDSNzAozYFbxJY&s=4RQH9NYEfO1Lwusgg_qaTX8-KgmRLqqpAHzOUNdgR6E&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2017_6_29_604&d=DwMGaQ&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=Ffjvk4Y8xEf_-aLPhDRUD2drOoDsZ0R_uiCBYAvmwAY&m=HxxYRqfeH8SOgZuryI2hIvUXHNgkHkYSOXflazJS-h8&s=bdN75Gm8T9CzT4mokKCWPHP8Inl5tibax6aU5mkibBM&e=> patchset tries to reduce, you can ignore the whole patchset and this fix.
    > 
    
>>    This is absolutely unreadable gunk. It's enough to refer to a commit sha
>>   instead of these horrible unformatted html style references.
I provided commit sha in addition to html references. Your email client might not have liked those reference (unfortunately). For some people, it will help easier to see code and I will not get into details/path.
In any cases, I'll stop providing those references in the futures. Thanks for the feedback.

 >> And please stop top posting and trim your replies.

Thanks
Chakri

    
    Thanks,
    
    	tglx