[PATCH 0/2] MediaTek SCP: Urgent fixes for all MTK SoCs

risks which I believe I really don't need to describe, leaving it to the reader's imagination :-) Please note that the first fix is URGENT. P.S.: Of course, this was tested OK on multiple MTK platforms. AngeloGioacchino Del Regno (2): remoteproc: mediatek: Make sure IPI buffer fits in L2TCM

Re: suspicious RCU usage warning on tracing/urgent

On Mon, 11 Sep 2023 12:00:53 +0900 Masami Hiramatsu (Google) wrote: > But it seems correctly taking srcu_read_lock(). > > 452 > 453 ei = ti->private; > 454 idx = srcu_read_lock(_srcu); > 455 list_for_each_entry_rcu(ef, >e_top_files, list) { > 456

suspicious RCU usage warning on tracing/urgent

Hi Steve, I got this suspicious RCU usage warning when I ran ftracetest on tracing/urgent branch. [1] Basic trace file check[ 17.172817] [ 17.174621] = [ 17.177730] WARNING: suspicious RCU usage [ 17.180962] 6.5.0-10750-g595efe1079cd #47 Tainted: G

[tip: x86/urgent] x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: 5849cdf8c120e3979c57d34be55b92d90a77a47e Gitweb: https://git.kernel.org/tip/5849cdf8c120e3979c57d34be55b92d90a77a47e Author:Mike Galbraith AuthorDate:Fri, 16 Apr 2021 14:02:07 +02:00

[tip: sched/urgent] preempt/dynamic: Fix typo in macro conditional statement

The following commit has been merged into the sched/urgent branch of tip: Commit-ID: 0c89d87d1d43d9fa268d1dc489518564d58bf497 Gitweb: https://git.kernel.org/tip/0c89d87d1d43d9fa268d1dc489518564d58bf497 Author:Zhouyi Zhou AuthorDate:Sat, 10 Apr 2021 15:35:23 +08:00

Re: [tip: x86/urgent] x86/dma: Tear down DMA ops on driver unbind

On Sat, Apr 17, 2021 at 02:06:44PM +0200, Borislav Petkov wrote: > Nope, sorry, no joy. Zapping it from tip. > > With that patch, it fails booting on my test box with messages like > (typing up from video I took): > > ... > ata: softreset failed (1st FIS failed) > ahci :03:00:1: AMD-Vi:

[tip:locking/urgent] BUILD SUCCESS 84a24bf8c52e66b7ac89ada5e3cfbe72d65c1896

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/urgent branch HEAD: 84a24bf8c52e66b7ac89ada5e3cfbe72d65c1896 locking/qrwlock: Fix ordering in queued_write_lock_slowpath() elapsed time: 723m configs tested: 119 configs skipped: 2 The following configs have

Re: [tip: x86/urgent] x86/dma: Tear down DMA ops on driver unbind

On Thu, Apr 15, 2021 at 09:00:57AM -, tip-bot2 for Jean-Philippe Brucker wrote: > The following commit has been merged into the x86/urgent branch of tip: > > Commit-ID: 9f8614f5567eb4e38579422d38a1bdfeeb648ffc > Gitweb: > https://git

[tip: locking/urgent] locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

The following commit has been merged into the locking/urgent branch of tip: Commit-ID: 84a24bf8c52e66b7ac89ada5e3cfbe72d65c1896 Gitweb: https://git.kernel.org/tip/84a24bf8c52e66b7ac89ada5e3cfbe72d65c1896 Author:Ali Saidi AuthorDate:Thu, 15 Apr 2021 17:27:11 Committer

PERSONAL TREAT AS URGENT.

Dear Friend, Greetings! How are you with your family today? I hope both of you are in good health decently, I know that this message might meet you in utmost surprise as we never know each other before. I am Mr. Dabire Basole a banker by profession, I need your urgent assist in transferring

[tip:x86/urgent] BUILD SUCCESS 9f8614f5567eb4e38579422d38a1bdfeeb648ffc

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent branch HEAD: 9f8614f5567eb4e38579422d38a1bdfeeb648ffc x86/dma: Tear down DMA ops on driver unbind elapsed time: 732m configs tested: 210 configs skipped: 79 The following configs have been built successfully

[tip: x86/urgent] x86/dma: Tear down DMA ops on driver unbind

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: 9f8614f5567eb4e38579422d38a1bdfeeb648ffc Gitweb: https://git.kernel.org/tip/9f8614f5567eb4e38579422d38a1bdfeeb648ffc Author:Jean-Philippe Brucker AuthorDate:Wed, 14 Apr 2021 10:26:34 +02:00

URGENT RESPONSE NEEDED.

Dear friend, i am contacting you independently of my investigation in my bank and no one is informed of this communication. I need your urgent assistance in transferring the sum of $5.3million dollars to your private account,that belongs to one of our foreign customer who died a longtime with his

Urgent Response

Dear friend, I am contacting you independently of my investigation in my bank and no one is informed of this communication. I need your urgent assistance in transferring the sum of $5.3 million dollars to your private account,that belongs to one of our foreign customers who died a longtime

Re: [GIT PULL] x86/urgent for v5.12-rc7

The pull request you sent on Sun, 11 Apr 2021 11:03:32 +0200: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > tags/x86_urgent_for_v5.12-rc7 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/06f838e02d3b6e161df08c910e12e8366f1cb465 Thank you! --

[GIT PULL] x86/urgent for v5.12-rc7

Hi Linus, please pull two more urgent fixes (not gonna say "final" this time) from x86-land. Thx. --- The following changes since commit e49d033bddf5b565044e2abe4241353959bc9120: Linux 5.12-rc6 (2021-04-04 14:15:36 -0700) are available in the Git repository at: git://git.kern

[tip:x86/urgent] BUILD SUCCESS 632a1c209b8773cb0119fe3aada9f1db14fa357c

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent branch HEAD: 632a1c209b8773cb0119fe3aada9f1db14fa357c x86/traps: Correct exc_general_protection() and math_error() return paths elapsed time: 725m configs tested: 223 configs skipped: 4 The following configs

Re: PLEASE TREAT AS URGENT

-- My Dearest, Please forgive me for stressing you with my predicaments as I know that this letter may come to you as big surprise. Actually, I came across your E-mail from my personal search afterward I decided to email you directly believing that you will be honest to fulfill my final wish

[tip: x86/urgent] x86/traps: Correct exc_general_protection() and math_error() return paths

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: 632a1c209b8773cb0119fe3aada9f1db14fa357c Gitweb: https://git.kernel.org/tip/632a1c209b8773cb0119fe3aada9f1db14fa357c Author:Thomas Tai AuthorDate:Thu, 08 Apr 2021 13:28:33 -04:00 Committer

PERSONAL TREAT AS URGENT.

Dear Friend, Greetings! How are you with your family today? I hope both of you are in good health decently, I know that this message might meet you in utmost surprise as we never know each other before. I am Mr. Dabire Basole a banker by profession, I need your urgent assist in transferring

[tip:x86/urgent] BUILD SUCCESS 3a62583c2853b0ab37a57dde79decea210b5fb89

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent branch HEAD: 3a62583c2853b0ab37a57dde79decea210b5fb89 RAS/CEC: Correct ce_add_elem()'s returned values elapsed time: 721m configs tested: 104 configs skipped: 3 The following configs have been built

[tip: x86/urgent] RAS/CEC: Correct ce_add_elem()'s returned values

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: 3a62583c2853b0ab37a57dde79decea210b5fb89 Gitweb: https://git.kernel.org/tip/3a62583c2853b0ab37a57dde79decea210b5fb89 Author:William Roche AuthorDate:Tue, 06 Apr 2021 11:28:59 -04:00

Your urgent response is needed

Dear Friend, With due respect, i have decided to contact you on a business transaction that will be beneficial to both of us. At the bank last account and auditing evaluation, my staffs came across an old account which was being maintained by a foreign client who we learn was among the deceased

[tip:locking/urgent] BUILD SUCCESS f2ea2c3568eb3852fcce1348f9dd56dbc12804c0

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/urgent branch HEAD: f2ea2c3568eb3852fcce1348f9dd56dbc12804c0 Merge branch 'locking/WIP' into locking/urgent elapsed time: 721m configs tested: 105 configs skipped: 2 The following configs have been built

i need your urgent help and assistance.

Dear Friend. I am Mr Yatmir Nutha. the director of the accounts & auditing department at the bank Ouagadougou-Burkina Faso in west Africa. With due respect, I have decided to contact you on a business transaction that will be beneficial to both of us. At the bank's last accounts/auditing

[tip:x86/urgent] BUILD SUCCESS 9fcb51c14da2953de585c5c6e50697b8a6e91a7b

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent branch HEAD: 9fcb51c14da2953de585c5c6e50697b8a6e91a7b x86/build: Turn off -fcf-protection for realmode targets elapsed time: 725m configs tested: 136 configs skipped: 49 The following configs have been built

[tip:locking/urgent] BUILD SUCCESS 291da9d4a9eb3a1cb0610b7f4480f5b52b1825e7

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/urgent branch HEAD: 291da9d4a9eb3a1cb0610b7f4480f5b52b1825e7 locking/mutex: Fix non debug version of mutex_lock_io_nested() elapsed time: 720m configs tested: 180 configs skipped: 2 The following configs have

[tip: x86/urgent] x86/build: Turn off -fcf-protection for realmode targets

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: 9fcb51c14da2953de585c5c6e50697b8a6e91a7b Gitweb: https://git.kernel.org/tip/9fcb51c14da2953de585c5c6e50697b8a6e91a7b Author:Arnd Bergmann AuthorDate:Tue, 23 Mar 2021 13:48:36 +01:00

[tip: x86/urgent] x86/mem_encrypt: Correct physical address calculation in __set_clr_pte_enc()

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: 8249d17d3194eac064a8ca5bc5ca0abc86feecde Gitweb: https://git.kernel.org/tip/8249d17d3194eac064a8ca5bc5ca0abc86feecde Author:Isaku Yamahata AuthorDate:Thu, 18 Mar 2021 13:26:57 -07:00

[tip: locking/urgent] locking/mutex: Fix non debug version of mutex_lock_io_nested()

The following commit has been merged into the locking/urgent branch of tip: Commit-ID: 291da9d4a9eb3a1cb0610b7f4480f5b52b1825e7 Gitweb: https://git.kernel.org/tip/291da9d4a9eb3a1cb0610b7f4480f5b52b1825e7 Author:Thomas Gleixner AuthorDate:Mon, 22 Mar 2021 09:46:13 +01:00

[tip:perf/urgent] BUILD SUCCESS 6d48b7912cc72275dc7c59ff961c8bac7ef66a92

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/urgent branch HEAD: 6d48b7912cc72275dc7c59ff961c8bac7ef66a92 lockdep: Address clang -Wformat warning printing for %hd elapsed time: 724m configs tested: 109 configs skipped: 2 The following configs have been built

[tip: perf/urgent] lockdep: Address clang -Wformat warning printing for %hd

The following commit has been merged into the perf/urgent branch of tip: Commit-ID: 6d48b7912cc72275dc7c59ff961c8bac7ef66a92 Gitweb: https://git.kernel.org/tip/6d48b7912cc72275dc7c59ff961c8bac7ef66a92 Author:Arnd Bergmann AuthorDate:Mon, 22 Mar 2021 12:55:25 +01:00

[tip:perf/urgent] BUILD SUCCESS 3a85969e9d912d5dd85362ee37b5f81266e00e77

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/urgent branch HEAD: 3a85969e9d912d5dd85362ee37b5f81266e00e77 lockdep: Add a missing initialization hint to the "INFO: Trying to register non-static key" message elapsed time: 722m configs tested: 133 confi

Re: [GIT PULL] x86/urgent for v5.12-rc4

The pull request you sent on Sun, 21 Mar 2021 12:01:58 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > tags/x86_urgent_for_v5.12-rc4 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/5e3ddf96e75983e4c404467fbb61b92d09333a1f Thank you! --

[tip: perf/urgent] lockdep: Add a missing initialization hint to the "INFO: Trying to register non-static key" message

The following commit has been merged into the perf/urgent branch of tip: Commit-ID: 3a85969e9d912d5dd85362ee37b5f81266e00e77 Gitweb: https://git.kernel.org/tip/3a85969e9d912d5dd85362ee37b5f81266e00e77 Author:Tetsuo Handa AuthorDate:Sun, 21 Mar 2021 15:49:13 +09:00

[GIT PULL] x86/urgent for v5.12-rc4

Hi Linus, please pull the freshest pile of shiny x86/urgent fixes for 5.12. Thx. --- The following changes since commit 1e28eed17697bcf343c6743f0028cc3b5dd88bf0: Linux 5.12-rc3 (2021-03-14 14:41:02 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel

[tip: irq/urgent] genirq: Disable interrupts for force threaded handlers

The following commit has been merged into the irq/urgent branch of tip: Commit-ID: 81e2073c175b887398e5bca6c004efa89983f58d Gitweb: https://git.kernel.org/tip/81e2073c175b887398e5bca6c004efa89983f58d Author:Thomas Gleixner AuthorDate:Wed, 17 Mar 2021 15:38:52 +01:00

[tip:x86/urgent] BUILD SUCCESS dd926880da8dbbe409e709c1d3c1620729a94732

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent branch HEAD: dd926880da8dbbe409e709c1d3c1620729a94732 x86/apic/of: Fix CPU devicetree-node lookups elapsed time: 727m configs tested: 131 configs skipped: 2 The following configs have been built successfully

[tip:efi/urgent] BUILD SUCCESS 429257a430a0e81e9979256e0db718e35e7d9cee

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi/urgent branch HEAD: 429257a430a0e81e9979256e0db718e35e7d9cee Merge tag 'efi-urgent-for-v5.12-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi into efi/urgent elapsed time: 721m configs tested: 148

[tip:locking/urgent] BUILD SUCCESS 38c93587375053c5b9ef093f4a5ea754538cba32

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/urgent branch HEAD: 38c93587375053c5b9ef093f4a5ea754538cba32 static_call: Fix static_call_update() sanity check elapsed time: 724m configs tested: 163 configs skipped: 2 The following configs have been built

[tip: x86/urgent] x86/apic/of: Fix CPU devicetree-node lookups

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: dd926880da8dbbe409e709c1d3c1620729a94732 Gitweb: https://git.kernel.org/tip/dd926880da8dbbe409e709c1d3c1620729a94732 Author:Johan Hovold AuthorDate:Fri, 12 Mar 2021 10:20:33 +01:00

[tip: efi/urgent] firmware/efi: Fix a use after bug in efi_mem_reserve_persistent

The following commit has been merged into the efi/urgent branch of tip: Commit-ID: 9ceee7d0841a8f7d7644021ba7d4cc1fbc7966e3 Gitweb: https://git.kernel.org/tip/9ceee7d0841a8f7d7644021ba7d4cc1fbc7966e3 Author:Lv Yunlong AuthorDate:Wed, 10 Mar 2021 00:31:27 -08:00 Committer

[tip: efi/urgent] efi: use 32-bit alignment for efi_guid_t literals

The following commit has been merged into the efi/urgent branch of tip: Commit-ID: fb98cc0b3af2ba4d87301dff2b381b12eee35d7d Gitweb: https://git.kernel.org/tip/fb98cc0b3af2ba4d87301dff2b381b12eee35d7d Author:Ard Biesheuvel AuthorDate:Wed, 10 Mar 2021 08:33:19 +01:00

[tip: efi/urgent] efivars: respect EFI_UNSUPPORTED return from firmware

The following commit has been merged into the efi/urgent branch of tip: Commit-ID: 483028edacab374060d93955382b4865a9e07cba Gitweb: https://git.kernel.org/tip/483028edacab374060d93955382b4865a9e07cba Author:Shawn Guo AuthorDate:Wed, 17 Mar 2021 14:36:06 +08:00 Committer

[tip: locking/urgent] static_call: Align static_call_is_init() patching condition

The following commit has been merged into the locking/urgent branch of tip: Commit-ID: 698bacefe993ad2922c9d3b1380591ad489355e9 Gitweb: https://git.kernel.org/tip/698bacefe993ad2922c9d3b1380591ad489355e9 Author:Peter Zijlstra AuthorDate:Thu, 18 Mar 2021 11:29:56 +01:00

[tip: locking/urgent] static_call: Fix static_call_update() sanity check

The following commit has been merged into the locking/urgent branch of tip: Commit-ID: 38c93587375053c5b9ef093f4a5ea754538cba32 Gitweb: https://git.kernel.org/tip/38c93587375053c5b9ef093f4a5ea754538cba32 Author:Peter Zijlstra AuthorDate:Thu, 18 Mar 2021 11:31:51 +01:00

[tip: locking/urgent] static_call: Fix static_call_set_init()

The following commit has been merged into the locking/urgent branch of tip: Commit-ID: 68b1eddd421d2b16c6655eceb48918a1e896bbbc Gitweb: https://git.kernel.org/tip/68b1eddd421d2b16c6655eceb48918a1e896bbbc Author:Peter Zijlstra AuthorDate:Thu, 18 Mar 2021 11:27:19 +01:00

[tip: x86/urgent] x86/ioapic: Ignore IRQ2 again

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: a501b048a95b79e1e34f03cac3c87ff1e9f229ad Gitweb: https://git.kernel.org/tip/a501b048a95b79e1e34f03cac3c87ff1e9f229ad Author:Thomas Gleixner AuthorDate:Thu, 18 Mar 2021 20:26:47 +01:00

[tip:locking/urgent] BUILD SUCCESS bee645788e07eea63055d261d2884ea45c2ba857

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/urgent branch HEAD: bee645788e07eea63055d261d2884ea45c2ba857 locking/ww_mutex: Fix acquire/release imbalance in ww_acquire_init()/ww_acquire_fini() elapsed time: 723m configs tested: 161 configs skipped: 3

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On 3/17/21 3:58 PM, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 02:32:27PM -0400, Waiman Long wrote: On 3/17/21 1:45 PM, Peter Zijlstra wrote: +# define __DEP_MAP_WW_MUTEX_INITIALIZER(lockname, class) \ + , .dep_map = { \ + .key = &(class).mutex_key, \ +

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On Wed, Mar 17, 2021 at 02:32:27PM -0400, Waiman Long wrote: > On 3/17/21 1:45 PM, Peter Zijlstra wrote: > > > +# define __DEP_MAP_WW_MUTEX_INITIALIZER(lockname, class) \ > > > + , .dep_map = { \ > > > + .key = &(class).mutex_key, \ > > > + .name =

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On 3/17/21 1:45 PM, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 06:40:27PM +0100, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 05:48:48PM +0100, Peter Zijlstra wrote: I think you'll find that if you use ww_mutex_init() it'll all work. Let me go and zap this patch, and then I'll try and

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On 3/17/21 1:40 PM, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 05:48:48PM +0100, Peter Zijlstra wrote: I think you'll find that if you use ww_mutex_init() it'll all work. Let me go and zap this patch, and then I'll try and figure out why DEFINE_WW_MUTEX() is buggered. Moo, I can't get the

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On Wed, Mar 17, 2021 at 06:40:27PM +0100, Peter Zijlstra wrote: > On Wed, Mar 17, 2021 at 05:48:48PM +0100, Peter Zijlstra wrote: > > > I think you'll find that if you use ww_mutex_init() it'll all work. Let > > me go and zap this patch, and then I'll try and figure out why > > DEFINE_WW_MUTEX()

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On Wed, Mar 17, 2021 at 05:48:48PM +0100, Peter Zijlstra wrote: > I think you'll find that if you use ww_mutex_init() it'll all work. Let > me go and zap this patch, and then I'll try and figure out why > DEFINE_WW_MUTEX() is buggered. Moo, I can't get the compiler to do as I want :/ The below

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On Wed, Mar 17, 2021 at 11:35:12AM -0400, Waiman Long wrote: > From reading the source code, nest_lock check is done in check_deadlock() so > that it won't complain. However, nest_lock isn't considered in > check_noncircular() which causes the splat to come out. Maybe we should add > a check for

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On 3/17/21 10:03 AM, Waiman Long wrote: On 3/17/21 9:31 AM, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 02:12:41PM +0100, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 12:38:21PM -, tip-bot2 for Waiman Long wrote: +    /* + * Treat as trylock for ww_mutex. + */ +   

Re: [tip: locking/urgent] locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling

On 3/17/21 10:10 AM, Waiman Long wrote: On 3/17/21 9:55 AM, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 09:43:20AM -0400, Waiman Long wrote: Using gcc 8.4.1, the generated __mutex_lock function has the same size (with last instruction at offset +5179) with or without this patch. Well, you

Re: [tip: locking/urgent] locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling

On Wed, Mar 17, 2021 at 10:10:16AM -0400, Waiman Long wrote: > On 3/17/21 9:55 AM, Peter Zijlstra wrote: > > On Wed, Mar 17, 2021 at 09:43:20AM -0400, Waiman Long wrote: > > > > > Using gcc 8.4.1, the generated __mutex_lock function has the same size > > > (with > > > last instruction at offset

Re: [tip: locking/urgent] locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling

On 3/17/21 9:55 AM, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 09:43:20AM -0400, Waiman Long wrote: Using gcc 8.4.1, the generated __mutex_lock function has the same size (with last instruction at offset +5179) with or without this patch. Well, you can say that this patch is an no-op wrt

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On 3/17/21 9:31 AM, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 02:12:41PM +0100, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 12:38:21PM -, tip-bot2 for Waiman Long wrote: + /* +* Treat as trylock for ww_mutex. +*/ + mutex_acquire_nest(>dep_map, subclass,

Re: [tip: locking/urgent] locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling

On Wed, Mar 17, 2021 at 09:43:20AM -0400, Waiman Long wrote: > Using gcc 8.4.1, the generated __mutex_lock function has the same size (with > last instruction at offset +5179) with or without this patch. Well, you can > say that this patch is an no-op wrt generated code. OK, then GCC has gotten

Re: [tip: locking/urgent] locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling

On 3/17/21 8:59 AM, Peter Zijlstra wrote: On Wed, Mar 17, 2021 at 12:38:22PM -, tip-bot2 for Waiman Long wrote: The following commit has been merged into the locking/urgent branch of tip: Commit-ID: 5de2055d31ea88fd9ae9709ac95c372a505a60fa Gitweb: https://git.kernel.org/tip

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On Wed, Mar 17, 2021 at 02:12:41PM +0100, Peter Zijlstra wrote: > On Wed, Mar 17, 2021 at 12:38:21PM -, tip-bot2 for Waiman Long wrote: > > + /* > > +* Treat as trylock for ww_mutex. > > +*/ > > + mutex_acquire_nest(>dep_map, subclass, !!ww_ctx, nest_lock, ip); > > I'm confused...

Re: [tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

On Wed, Mar 17, 2021 at 12:38:21PM -, tip-bot2 for Waiman Long wrote: > The following commit has been merged into the locking/urgent branch of tip: > > Commit-ID: b058f2e4d0a70c060e21ed122b264e9649cad57f > Gitweb: > https://git

Re: [tip: locking/urgent] locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling

On Wed, Mar 17, 2021 at 12:38:22PM -, tip-bot2 for Waiman Long wrote: > The following commit has been merged into the locking/urgent branch of tip: > > Commit-ID: 5de2055d31ea88fd9ae9709ac95c372a505a60fa > Gitweb: > https://git

[tip: perf/urgent] perf/x86/intel: Fix a crash caused by zero PEBS status

The following commit has been merged into the perf/urgent branch of tip: Commit-ID: d88d05a9e0b6d9356e97129d4ff9942d765f46ea Gitweb: https://git.kernel.org/tip/d88d05a9e0b6d9356e97129d4ff9942d765f46ea Author:Kan Liang AuthorDate:Fri, 12 Mar 2021 05:21:37 -08:00 Committer

[tip: perf/urgent] perf/x86/intel: Fix unchecked MSR access error caused by VLBR_EVENT

The following commit has been merged into the perf/urgent branch of tip: Commit-ID: 2dc0572f2cef87425147658698dce2600b799bd3 Gitweb: https://git.kernel.org/tip/2dc0572f2cef87425147658698dce2600b799bd3 Author:Kan Liang AuthorDate:Fri, 12 Mar 2021 05:21:38 -08:00 Committer

[tip: locking/urgent] locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling

The following commit has been merged into the locking/urgent branch of tip: Commit-ID: 5de2055d31ea88fd9ae9709ac95c372a505a60fa Gitweb: https://git.kernel.org/tip/5de2055d31ea88fd9ae9709ac95c372a505a60fa Author:Waiman Long AuthorDate:Tue, 16 Mar 2021 11:31:16 -04:00

[tip: locking/urgent] locking/ww_mutex: Fix acquire/release imbalance in ww_acquire_init()/ww_acquire_fini()

The following commit has been merged into the locking/urgent branch of tip: Commit-ID: bee645788e07eea63055d261d2884ea45c2ba857 Gitweb: https://git.kernel.org/tip/bee645788e07eea63055d261d2884ea45c2ba857 Author:Waiman Long AuthorDate:Tue, 16 Mar 2021 11:31:17 -04:00

[tip: locking/urgent] locking/ww_mutex: Treat ww_mutex_lock() like a trylock

The following commit has been merged into the locking/urgent branch of tip: Commit-ID: b058f2e4d0a70c060e21ed122b264e9649cad57f Gitweb: https://git.kernel.org/tip/b058f2e4d0a70c060e21ed122b264e9649cad57f Author:Waiman Long AuthorDate:Tue, 16 Mar 2021 11:31:18 -04:00

[tip:x86/urgent] BUILD SUCCESS b2e9df850c58c2b36e915e7d3bed3f6107cccba6

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent branch HEAD: b2e9df850c58c2b36e915e7d3bed3f6107cccba6 x86: Introduce restart_block->arch_data to remove TS_COMPAT_RESTART elapsed time: 722m configs tested: 138 configs skipped: 2 The following configs h

[tip:irq/urgent] BUILD SUCCESS ef4cb70a4c22bf301cd757dcc838dc8ca9526477

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/urgent branch HEAD: ef4cb70a4c22bf301cd757dcc838dc8ca9526477 genirq/irq_sim: Fix typos in kernel doc (fnode -> fwnode) elapsed time: 722m configs tested: 155 configs skipped: 2 The following configs have been bu

[tip: x86/urgent] kernel, fs: Introduce and use set_restart_fn() and arch_set_restart_data()

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: 5abbe51a526253b9f003e9a0a195638dc882d660 Gitweb: https://git.kernel.org/tip/5abbe51a526253b9f003e9a0a195638dc882d660 Author:Oleg Nesterov AuthorDate:Mon, 01 Feb 2021 18:46:41 +01:00

[tip: x86/urgent] x86: Introduce TS_COMPAT_RESTART to fix get_nr_restart_syscall()

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: 8c150ba2fb5995c84a7a43848250d444a3329a7d Gitweb: https://git.kernel.org/tip/8c150ba2fb5995c84a7a43848250d444a3329a7d Author:Oleg Nesterov AuthorDate:Mon, 01 Feb 2021 18:47:09 +01:00

[tip: x86/urgent] x86: Move TS_COMPAT back to asm/thread_info.h

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: 66c1b6d74cd7035e85c426f0af4aede19e805c8a Gitweb: https://git.kernel.org/tip/66c1b6d74cd7035e85c426f0af4aede19e805c8a Author:Oleg Nesterov AuthorDate:Mon, 01 Feb 2021 18:46:49 +01:00

[tip: x86/urgent] x86: Introduce restart_block->arch_data to remove TS_COMPAT_RESTART

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: b2e9df850c58c2b36e915e7d3bed3f6107cccba6 Gitweb: https://git.kernel.org/tip/b2e9df850c58c2b36e915e7d3bed3f6107cccba6 Author:Oleg Nesterov AuthorDate:Mon, 01 Feb 2021 18:47:16 +01:00

[tip: irq/urgent] genirq/irq_sim: Fix typos in kernel doc (fnode -> fwnode)

The following commit has been merged into the irq/urgent branch of tip: Commit-ID: ef4cb70a4c22bf301cd757dcc838dc8ca9526477 Gitweb: https://git.kernel.org/tip/ef4cb70a4c22bf301cd757dcc838dc8ca9526477 Author:Andy Shevchenko AuthorDate:Tue, 02 Mar 2021 18:14:53 +02:00

I NEED YOUR URGENT ASSISTANCE.

Please forgive me for stressing you with my predicaments and I sorry to approach you through this media it is because it serves the fastest means of communication. I came across your E-mail from my personal search and I decided to contact you believing you will be honest to fulfill my final wish

TREAT AS URGENT

Business Trustee Needed Urgently. Compliment of the day. I will like to discuss a Long-Term Business Opportunity with you. Kindly contact me back for more details and information. It’s a lucrative Mutual Business Venture. I await your prompt response. Regards, LEGAL EDGE Sheather Artemia

Re: [GIT pull] locking/urgent for v5.12-rc3

On Mon, Mar 15, 2021 at 11:59:12AM -0700, Linus Torvalds wrote: > Is it only the static_call_sites entry itself that needs the > alignment? Or do we end up depending on the static call function being > at least 4-byte aligned too? The way it plays games with the key makes > me worry. The only

Re: [GIT pull] locking/urgent for v5.12-rc3

On Mon, Mar 15, 2021 at 10:03 AM Josh Poimboeuf wrote: > > Though instead of using objtool, it can be done in the module linker > script: This is obviously the way to go, but it raises another question: do we guarantee that functions are aligned? We actually have a couple of 32-bit x86

Re: [GIT pull] locking/urgent for v5.12-rc3

On Mon, Mar 15, 2021 at 12:03:21PM -0500, Josh Poimboeuf wrote: > On Mon, Mar 15, 2021 at 01:08:27PM +0100, Peter Zijlstra wrote: > > On Mon, Mar 15, 2021 at 12:26:12PM +0100, Peter Zijlstra wrote: > > > Ooooh, modules don't have this. They still have regular > > > .static_call_sites sections, and

YOUR URGENT RESPONSE IS NEEDED NOW

-- I am contacting you on a business deal of $17.5 Million US Dollars, ready for transfer into your account if we make this claim, we will share it 60%/40%.100% risk free and it will be legally backed up with government approved If you are interested reply for more details. Kindly reply for

Re: [GIT pull] locking/urgent for v5.12-rc3

On Mon, Mar 15, 2021 at 01:08:27PM +0100, Peter Zijlstra wrote: > On Mon, Mar 15, 2021 at 12:26:12PM +0100, Peter Zijlstra wrote: > > Ooooh, modules don't have this. They still have regular > > .static_call_sites sections, and *those* are unaligned. > > > > Section Headers: > > [Nr] Name

Re: [GIT pull] locking/urgent for v5.12-rc3

On Mon, 15 Mar 2021 13:08:27 +0100 Peter Zijlstra wrote: > So, anybody any opinion on if we ought to do this? Looks fine to me. -- Steve

Re: [GIT pull] locking/urgent for v5.12-rc3

On Mon, Mar 15, 2021 at 12:26:12PM +0100, Peter Zijlstra wrote: > Ooooh, modules don't have this. They still have regular > .static_call_sites sections, and *those* are unaligned. > > Section Headers: > [Nr] Name TypeAddress OffSize ES Flg > Lk Inf Al > >

Re: [GIT pull] locking/urgent for v5.12-rc3

On Mon, Mar 15, 2021 at 12:10:10PM +0100, Peter Zijlstra wrote: > On Mon, Mar 15, 2021 at 09:33:45AM +0100, Peter Zijlstra wrote: > > On Sun, Mar 14, 2021 at 01:15:25PM -0700, Linus Torvalds wrote: > > > On Sun, Mar 14, 2021 at 8:40 AM Thomas Gleixner > > > wrote: > > > > > > > > - A fix for

Re: [GIT pull] locking/urgent for v5.12-rc3

On Mon, Mar 15, 2021 at 09:33:45AM +0100, Peter Zijlstra wrote: > On Sun, Mar 14, 2021 at 01:15:25PM -0700, Linus Torvalds wrote: > > On Sun, Mar 14, 2021 at 8:40 AM Thomas Gleixner wrote: > > > > > > - A fix for the static_call mechanism so it handles unaligned > > >addresses correctly. > >

I sent you a mail earlier but not sure if you received it, kindly check your email and get back to me for I have very urgent information to pass to you.

Re: [GIT pull] locking/urgent for v5.12-rc3

On Sun, Mar 14, 2021 at 01:15:25PM -0700, Linus Torvalds wrote: > On Sun, Mar 14, 2021 at 8:40 AM Thomas Gleixner wrote: > > > > - A fix for the static_call mechanism so it handles unaligned > >addresses correctly. > > I'm not disputing the fix in any way, but why weren't the relocation >

Re: [GIT pull] timers/urgent for v5.12-rc3

The pull request you sent on Sun, 14 Mar 2021 15:40:00 -: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > timers-urgent-2021-03-14 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/802b31c0dd7f44c9ab44d39c6c4af22d958ad803 Thank you! -- Deet-do

Re: [GIT pull] locking/urgent for v5.12-rc3

The pull request you sent on Sun, 14 Mar 2021 15:39:56 -: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > locking-urgent-2021-03-14 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/fa509ff879f816ce50800d20fc87564b69f53962 Thank you! -- Dee

Re: [GIT pull] sched/urgent for v5.12-rc3

The pull request you sent on Sun, 14 Mar 2021 15:39:59 -: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > sched-urgent-2021-03-14 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/c72cbc936141eac737b24f43e742cefaab35edd6 Thank you! -- Deet-do

Re: [GIT pull] objtool/urgent for v5.12-rc3

The pull request you sent on Sun, 14 Mar 2021 15:39:57 -: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > objtool-urgent-2021-03-14 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/19469d2adab9a94e3c1713b7a12a67f9c59c1161 Thank you! -- Dee

Re: [GIT pull] irq/urgent for v5.12-rc2

The pull request you sent on Sun, 14 Mar 2021 15:40:01 -: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > irq-urgent-2021-03-14 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/70404fe3030ec2dcf339a9730bc03bf0e1f2acf5 Thank you! -- Deet-doot-

Re: [GIT pull] locking/urgent for v5.12-rc3

On Sun, Mar 14, 2021 at 8:40 AM Thomas Gleixner wrote: > > - A fix for the static_call mechanism so it handles unaligned >addresses correctly. I'm not disputing the fix in any way, but why weren't the relocation info and function start addresses mutually aligned? Are we perhaps missing

Re: [GIT PULL] x86/urgent for v5.12-rc3

The pull request you sent on Sun, 14 Mar 2021 13:07:26 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > tags/x86_urgent_for_v5.12_rc3 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/0a7c10df49eb69dd888ea8b8ddd29bde2aa2fd48 Thank you! --

Re: [GIT PULL] perf/urgent for v5.12-rc3

The pull request you sent on Sun, 14 Mar 2021 13:44:11 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > tags/perf_urgent_for_v5.12-rc3 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/75013c6c52d80b2255ba273eedac013d58754b02 Thank you! --

Re: [GIT PULL] efi/urgent for v5.12-rc3

The pull request you sent on Sun, 14 Mar 2021 13:21:47 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > tags/efi-urgent-for-v5.12-rc2 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/836d7f0572ca42ac85d649235680479740743ac6 Thank you! --

  1   2   3   4   5   6   7   8   9   10   >