[cctalk] Re: Double Density 3.5" Floppy Disks

2024-05-06 Thread Mike Stein via cctalk
of these days (that one minute on, 30 minute off (officially ;-) duty cycle is a PITA if you're degaussing a bunch of disks). On Mon, May 6, 2024 at 9:42 PM Mike Katz via cctalk wrote: > I also have one of those from Radio Shack that I have had for more than > 30 years. > > On 5/6/2024 8:30 PM,

[cctalk] Re: Double Density 3.5" Floppy Disks

2024-05-06 Thread Mike Katz via cctalk
I also have one of those from Radio Shack that I have had for more than 30 years. On 5/6/2024 8:30 PM, Chuck Guzis via cctalk wrote: On 5/6/24 15:12, Fred Cisin via cctalk wrote: Radio Shack used to sell a "Bulk Tape Eraser".  I gave mine to the college. Those are on eBay, and even Amazon.

Re: Question about iPhone case

2024-05-06 Thread Mike B
Hi Rena, Here's there direct phone number and URL. If you call them they are very very helpful. 1-855-688-7269 https://www.otterbox.com/ Take care and stay safe. Mike. Sent from my iBarstool! Go Dodgers! - Original Message - From: Rena To: viphone@googlegroups.com Sent: Monday

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/linux-docs/

2024-05-06 Thread Mike Pagano
commit: e86353f613c855ccedd91cdba8245057ff3ecb14 Author: Mike Pagano gentoo org> AuthorDate: Mon May 6 22:44:47 2024 + Commit: Mike Pagano gentoo org> CommitDate: Mon May 6 22:44:47 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e86353f

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/linux-docs/

2024-05-06 Thread Mike Pagano
commit: 4cfd6426a146520696474b1f47827ab18ba5b5e3 Author: Mike Pagano gentoo org> AuthorDate: Mon May 6 22:45:08 2024 + Commit: Mike Pagano gentoo org> CommitDate: Mon May 6 22:45:08 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4cfd642

comment on Entrust_Issues wiki page

2024-05-06 Thread Mike Shaver
st or the IR until April 10th. No comment was made about a delay, or the reason that it was necessary. Mike -- You received this message because you are subscribed to the Google Groups "dev-security-policy@mozilla.org" group. To unsubscribe from this group and stop receiving emails

[jira] [Created] (DAFFODIL-2897) change scalafmt back to rewrite.trailingCommas.style 'never'

2024-05-06 Thread Mike Beckerle (Jira)
Mike Beckerle created DAFFODIL-2897: --- Summary: change scalafmt back to rewrite.trailingCommas.style 'never' Key: DAFFODIL-2897 URL: https://issues.apache.org/jira/browse/DAFFODIL-2897 Project

[jira] [Assigned] (DAFFODIL-2897) change scalafmt back to rewrite.trailingCommas.style 'never'

2024-05-06 Thread Mike Beckerle (Jira)
[ https://issues.apache.org/jira/browse/DAFFODIL-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Beckerle reassigned DAFFODIL-2897: --- Assignee: Mike Beckerle > change scalafmt back to rewrite.trailingCommas.st

Re: [PATCH] scsi:iscsi: Remove unused list 'connlist_err'

2024-05-06 Thread 'Mike Christie' via open-iscsi
NE_SPINLOCK(connlock); > > static uint32_t iscsi_conn_get_sid(struct iscsi_cls_conn *conn) Reviewed-by: Mike Christie -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it

Bug#758985: libsqlite3-0: Please support 'icu' and 'unicode61' tokenizers

2024-05-06 Thread Mike Gabriel
applications with the new-featured sqlite3. I can help with communications if needed. Please let me know. Thanks! Looking forward to seeing this addressed in short-term... Mike [1] https://ftp-master.debian.org/new/qtcontacts-sqlite_0.3.5-1.html [2] https://lomiri.com [3] https://gitlab

Re: [GUAC] Using with AAD Joined RDP w/ NLA?

2024-05-06 Thread Mike
of the machine, IP address wont work.  I doubt Guacamole can pass through the web sign in though.   My best guess is that the only way is to disable NLA but will be happy to be told I am wrong. -mike On Monday, May 6, 2024 at 01:00:30 PM EDT, Daniel Carroll wrote: By Entra-joined, you mean

Re: GESO: A bonanza of dakotas

2024-05-06 Thread mike wilson
And a nice Convair. We don't see those over here. In fact, any delta wing except for various Mirages and the (very) odd SAAB is quite unusual. > On 05/05/2024 22:47 BST Larry Colen wrote: > > > I first saw this airport on a hike about a year ago, I finally rode my bike > down to Flabob

[systemsettings] [Bug 486167] Install of Epson ET-8550 network printer won't complete - Printer not discovered on network

2024-05-06 Thread Mike
https://bugs.kde.org/show_bug.cgi?id=486167 --- Comment #5 from Mike --- (In reply to wal9 from comment #4) > (In reply to Mike from comment #3) > > Can you remove the printer and try again, this time choose the "Driverless" > > option when displayed? > > I cou

Using with AAD Joined RDP w/ NLA?

2024-05-06 Thread Mike
Hi, I am wondering if anyone is successfully using Guacamole with AAD-Joined (Entra-joined) windows desktops w/ RDP without having to disable NLA? Thanks Mike

[cytoscape/cytoscape.js] 5d09bd: Add cy.renderedExtent() to docs

2024-05-06 Thread 'Mike Kucera' via cytoscape-cvs
Branch: refs/heads/unstable Home: https://github.com/cytoscape/cytoscape.js Commit: 5d09bdff993af962c206d216147a37044b4a36a1 https://github.com/cytoscape/cytoscape.js/commit/5d09bdff993af962c206d216147a37044b4a36a1 Author: Mike Kucera Date: 2024-05-06 (Mon, 06 May 2024

[#347534] FAILED srpm=sispmctl-4.12-alt1.src.rpm

2024-05-06 Thread Girar awaiter (mike)
https://git.altlinux.org/tasks/347534/logs/events.1.1.log subtask name aarch64 i586 ppc64le x86_64 #100 sispmctl 4531 52 31 2024-May-06 07:55:09 :: task #347534 for sisyphus started by mike: #100 build sispmctl-4.12-alt1.src.rpm 2024-May-06 07:55:11 :: [ppc64le

rainloop 1.17.0 and php82 issue

2024-05-05 Thread Mike
I currently have rainloop 1.17.0 running quite nicely with php81 and php81-extensions. However, when I change the 81 to 82 above, I am greeted with the following error message when I try to use rainloop: Deprecated: Creation of dynamic property RainLoop\Actions::$bIsAjax is deprecated in

Re: [AFMUG] DWDM/CWDM Magic

2024-05-05 Thread Mike Hammett
$700 seems to be Zayo's floor. - Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP - Original Message - From: "Zach Underwood" To: "AnimalFarm Microwave Users Group" Sent: Friday, May 3, 2024 10:27:33 PM

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/git-sources/

2024-05-05 Thread Mike Pagano
commit: 7d1456adbb45b7eb419cdaa19d62c018f6257601 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 21:20:56 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 21:21:06 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7d1456a

Bug#1070468: ITP: qtcontacts-sqlite -- SQLite-based plugin for QtPIM Contacts

2024-05-05 Thread Mike Gabriel
Package: wnpp Severity: wishlist Owner: Mike Gabriel X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: qtcontacts-sqlite Version : 0.3.5 Upstream Contact: Alberto Mardegan * URL : https://gitlab.com/ubports/development/core/qtcontacts-sqlite * License

Bug#1070468: ITP: qtcontacts-sqlite -- SQLite-based plugin for QtPIM Contacts

2024-05-05 Thread Mike Gabriel
Package: wnpp Severity: wishlist Owner: Mike Gabriel X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: qtcontacts-sqlite Version : 0.3.5 Upstream Contact: Alberto Mardegan * URL : https://gitlab.com/ubports/development/core/qtcontacts-sqlite * License

Bug#1070468: ITP: qtcontacts-sqlite -- SQLite-based plugin for QtPIM Contacts

2024-05-05 Thread Mike Gabriel
Package: wnpp Severity: wishlist Owner: Mike Gabriel X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: qtcontacts-sqlite Version : 0.3.5 Upstream Contact: Alberto Mardegan * URL : https://gitlab.com/ubports/development/core/qtcontacts-sqlite * License

Bug#1070455: ayatana-indicator-display: FTBFS: Errors while running CTest

2024-05-05 Thread Mike Gabriel
2 make: *** [debian/rules:21: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 The above is just how the build ends and not necessarily the most relevant part. If requi

Bug#1070455: ayatana-indicator-display: FTBFS: Errors while running CTest

2024-05-05 Thread Mike Gabriel
2 make: *** [debian/rules:21: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 The above is just how the build ends and not necessarily the most relevant part. If requi

PC Sensors TEMPer sensor oddity...

2024-05-05 Thread Mike
Running OpenBSD 7.5 on AMD64. Full dmesg is at the end of this message. This sensor used to work well with OpenBSD 7.4. Since I moved to 7.5, the following issue is reproducible... The sensor is plugged into the USB port, and the PC (in this case, laptop) is powered up. After the boot is

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/linux-docs/

2024-05-05 Thread Mike Pagano
commit: c496cc406719b79ce736d95cd3a2019129e5fdc4 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 18:46:39 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 18:46:39 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c496cc4

[gentoo-commits] proj/linux-patches:5.10 commit in: /

2024-05-05 Thread Mike Pagano
commit: c623a513a581cbd0a45d7ea015ddb22c2e452137 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 18:13:49 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 18:13:49 2024 + URL:https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=c6

[gentoo-commits] proj/linux-patches:5.15 commit in: /

2024-05-05 Thread Mike Pagano
commit: e950ae435e3bfcc91ded4cfda5e18d5586d3168c Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 18:11:31 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 18:11:31 2024 + URL:https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=e9

[gentoo-commits] proj/linux-patches:6.1 commit in: /

2024-05-05 Thread Mike Pagano
commit: 5d2714f1df1d6389f8b3907e9264f212004ae185 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 18:09:49 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 18:09:49 2024 + URL:https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=5d

[gentoo-commits] proj/linux-patches:6.6 commit in: /

2024-05-05 Thread Mike Pagano
commit: 6188b97edf588f87d24e35068083a8561d152f91 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 17:54:13 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 18:06:28 2024 + URL:https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=61

[gentoo-commits] proj/linux-patches:6.9 commit in: /

2024-05-05 Thread Mike Pagano
commit: bf5362e40b7eaa6ea37b4205fdc8f6f106de74d9 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 17:54:13 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 18:02:15 2024 + URL:https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=bf

[gentoo-commits] proj/linux-patches:6.8 commit in: /

2024-05-05 Thread Mike Pagano
commit: 9dcf8bea816a2e0a4ee33c00c855bd27a5253e7f Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 17:54:13 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 18:01:54 2024 + URL:https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=9d

[gentoo-commits] proj/linux-patches:6.8 commit in: /

2024-05-05 Thread Mike Pagano
commit: 54d1b8f05b1a9bb154b528bda020c5c1b9143e51 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 18:00:38 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 18:00:38 2024 + URL:https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=54

[gentoo-commits] proj/linux-patches:master commit in: /

2024-05-05 Thread Mike Pagano
commit: abbbd285be43f4a758e4cbaac9cf33c6bc74e32a Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 17:54:13 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 17:54:13 2024 + URL:https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=ab

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/gentoo-sources/

2024-05-05 Thread Mike Pagano
commit: d96b271e8faf43a045093be5a863b8f2ad8bdd32 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 16:32:01 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 16:32:01 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d96b271

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/gentoo-sources/

2024-05-05 Thread Mike Pagano
commit: 3c056cc7deb7dc07a2b847cd8896461e44015064 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 16:32:20 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 16:32:20 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3c056cc

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/gentoo-sources/

2024-05-05 Thread Mike Pagano
commit: b61ac208e210257462ff311070698f10a1edeab4 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 16:32:10 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 16:32:10 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b61ac20

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/gentoo-sources/

2024-05-05 Thread Mike Pagano
commit: 3ba014424e378e3dd16828cd9d5facc74a1c0fb4 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 16:31:49 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 16:31:49 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3ba0144

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/gentoo-sources/

2024-05-05 Thread Mike Pagano
commit: fa4956c54195eb2bc3bec97cb8e266e705334e75 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 16:30:15 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 16:30:15 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fa4956c

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/gentoo-sources/

2024-05-05 Thread Mike Pagano
commit: 6201d6cdb113309868b20b07bc248c80018b4930 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 16:30:35 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 16:30:35 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6201d6c

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/gentoo-sources/

2024-05-05 Thread Mike Pagano
commit: 3854332ddeb88b94d49108ab2a7fd54f32740897 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 16:30:00 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 16:30:00 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3854332

[gentoo-commits] repo/gentoo:master commit in: sys-kernel/gentoo-sources/

2024-05-05 Thread Mike Pagano
commit: 363e6fe4d31c32b026040749e792938d06e4b013 Author: Mike Pagano gentoo org> AuthorDate: Sun May 5 16:29:37 2024 + Commit: Mike Pagano gentoo org> CommitDate: Sun May 5 16:29:37 2024 + URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=363e6fe

Re: [PATCH v8 00/17] mm: jit/text allocator

2024-05-05 Thread Mike Rapoport
This is embarrassing, but these patches were from a wrong branch :( Please ignore. On Sun, May 05, 2024 at 05:25:43PM +0300, Mike Rapoport wrote: > From: "Mike Rapoport (IBM)" > > Hi, > > The patches are also available in git: > https://git.kernel.org/pub/scm/lin

Re: [PATCH v8 00/17] mm: jit/text allocator

2024-05-05 Thread Mike Rapoport
This is embarrassing, but these patches were from a wrong branch :( Please ignore. On Sun, May 05, 2024 at 05:25:43PM +0300, Mike Rapoport wrote: > From: "Mike Rapoport (IBM)" > > Hi, > > The patches are also available in git: > https://git.kernel.org/pub/scm/lin

[PATCH RESEND v8 16/16] bpf: remove CONFIG_BPF_JIT dependency on CONFIG_MODULES of

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" BPF just-in-time compiler depended on CONFIG_MODULES because it used module_alloc() to allocate memory for the generated code. Since code allocations are now implemented with execmem, drop dependency of CONFIG_BPF_JIT on CONFIG_MODULES and make

[PATCH RESEND v8 15/16] kprobes: remove dependency on CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" kprobes depended on CONFIG_MODULES because it has to allocate memory for code. Since code allocations are now implemented with execmem, kprobes can be enabled in non-modular kernels. Add #ifdef CONFIG_MODULE guards for the code dealing with kprobes insi

[PATCH RESEND v8 14/16] powerpc: use CONFIG_EXECMEM instead of CONFIG_MODULES where appropriate

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" There are places where CONFIG_MODULES guards the code that depends on memory allocation being done with module_alloc(). Replace CONFIG_MODULES with CONFIG_EXECMEM in such places. Signed-off-by: Mike Rapoport (IBM) --- arch/powerpc/Kconfig

[PATCH RESEND v8 13/16] x86/ftrace: enable dynamic ftrace without CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Dynamic ftrace must allocate memory for code and this was impossible without CONFIG_MODULES. With execmem separated from the modules code, execmem_text_alloc() is available regardless of CONFIG_MODULES. Remove dependency of dynamic ftrace on CONFIG_MODULE

[PATCH RESEND v8 12/16] arch: make execmem setup available regardless of CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" execmem does not depend on modules, on the contrary modules use execmem. To make execmem available when CONFIG_MODULES=n, for instance for kprobes, split execmem_params initialization out from arch/*/kernel/module.c and compile it when CONFIG_EXECMEM=y

[PATCH RESEND v8 11/16] powerpc: extend execmem_params for kprobes allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" powerpc overrides kprobes::alloc_insn_page() to remove writable permissions when STRICT_MODULE_RWX is on. Add definition of EXECMEM_KRPOBES to execmem_params to allow using the generic kprobes::alloc_insn_page() with the desired permissions. As po

[PATCH RESEND v8 10/16] arm64: extend execmem_info for generated code allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" The memory allocations for kprobes and BPF on arm64 can be placed anywhere in vmalloc address space and currently this is implemented with overrides of alloc_insn_page() and bpf_jit_alloc_exec() in arm64. Define EXECMEM_KPROBES and EXECMEM_BPF range

[PATCH RESEND v8 09/16] riscv: extend execmem_params for generated code allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" The memory allocations for kprobes and BPF on RISC-V are not placed in the modules area and these custom allocations are implemented with overrides of alloc_insn_page() and bpf_jit_alloc_exec(). Define MODULES_VADDR and MODULES_END as VMALLOC_START and V

[PATCH RESEND v8 16/16] bpf: remove CONFIG_BPF_JIT dependency on CONFIG_MODULES of

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" BPF just-in-time compiler depended on CONFIG_MODULES because it used module_alloc() to allocate memory for the generated code. Since code allocations are now implemented with execmem, drop dependency of CONFIG_BPF_JIT on CONFIG_MODULES and make

[PATCH RESEND v8 08/16] mm/execmem, arch: convert remaining overrides of module_alloc to execmem

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Extend execmem parameters to accommodate more complex overrides of module_alloc() by architectures. This includes specification of a fallback range required by arm, arm64 and powerpc, EXECMEM_MODULE_DATA type required by powerpc, support for allocatio

[PATCH RESEND v8 15/16] kprobes: remove dependency on CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" kprobes depended on CONFIG_MODULES because it has to allocate memory for code. Since code allocations are now implemented with execmem, kprobes can be enabled in non-modular kernels. Add #ifdef CONFIG_MODULE guards for the code dealing with kprobes insi

[PATCH RESEND v8 14/16] powerpc: use CONFIG_EXECMEM instead of CONFIG_MODULES where appropriate

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" There are places where CONFIG_MODULES guards the code that depends on memory allocation being done with module_alloc(). Replace CONFIG_MODULES with CONFIG_EXECMEM in such places. Signed-off-by: Mike Rapoport (IBM) --- arch/powerpc/Kconfig

[PATCH RESEND v8 07/16] mm/execmem, arch: convert simple overrides of module_alloc to execmem

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Several architectures override module_alloc() only to define address range for code allocations different than VMALLOC address space. Provide a generic implementation in execmem that uses the parameters for address space ranges, required alignmen

[PATCH RESEND v8 13/16] x86/ftrace: enable dynamic ftrace without CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Dynamic ftrace must allocate memory for code and this was impossible without CONFIG_MODULES. With execmem separated from the modules code, execmem_text_alloc() is available regardless of CONFIG_MODULES. Remove dependency of dynamic ftrace on CONFIG_MODULE

[PATCH RESEND v8 12/16] arch: make execmem setup available regardless of CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" execmem does not depend on modules, on the contrary modules use execmem. To make execmem available when CONFIG_MODULES=n, for instance for kprobes, split execmem_params initialization out from arch/*/kernel/module.c and compile it when CONFIG_EXECMEM=y

[PATCH RESEND v8 06/16] mm: introduce execmem_alloc() and execmem_free()

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" module_alloc() is used everywhere as a mean to allocate memory for code. Beside being semantically wrong, this unnecessarily ties all subsystems that need to allocate code, such as ftrace, kprobes and BPF to modules and puts the burden of code

[PATCH RESEND v8 11/16] powerpc: extend execmem_params for kprobes allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" powerpc overrides kprobes::alloc_insn_page() to remove writable permissions when STRICT_MODULE_RWX is on. Add definition of EXECMEM_KRPOBES to execmem_params to allow using the generic kprobes::alloc_insn_page() with the desired permissions. As po

[PATCH RESEND v8 05/16] module: make module_memory_{alloc,free} more self-contained

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Move the logic related to the memory allocation and freeing into module_memory_alloc() and module_memory_free(). Signed-off-by: Mike Rapoport (IBM) Reviewed-by: Philippe Mathieu-Daudé --- kernel/module/main.c | 64 +++--

[PATCH RESEND v8 10/16] arm64: extend execmem_info for generated code allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" The memory allocations for kprobes and BPF on arm64 can be placed anywhere in vmalloc address space and currently this is implemented with overrides of alloc_insn_page() and bpf_jit_alloc_exec() in arm64. Define EXECMEM_KPROBES and EXECMEM_BPF range

[PATCH RESEND v8 09/16] riscv: extend execmem_params for generated code allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" The memory allocations for kprobes and BPF on RISC-V are not placed in the modules area and these custom allocations are implemented with overrides of alloc_insn_page() and bpf_jit_alloc_exec(). Define MODULES_VADDR and MODULES_END as VMALLOC_START and V

[PATCH RESEND v8 08/16] mm/execmem, arch: convert remaining overrides of module_alloc to execmem

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Extend execmem parameters to accommodate more complex overrides of module_alloc() by architectures. This includes specification of a fallback range required by arm, arm64 and powerpc, EXECMEM_MODULE_DATA type required by powerpc, support for allocatio

[PATCH RESEND v8 04/16] sparc: simplify module_alloc()

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Define MODULES_VADDR and MODULES_END as VMALLOC_START and VMALLOC_END for 32-bit and reduce module_alloc() to __vmalloc_node_range(size, 1, MODULES_VADDR, MODULES_END, ...) as with the new defines the allocations becomes identical for both 32 a

[PATCH RESEND v8 07/16] mm/execmem, arch: convert simple overrides of module_alloc to execmem

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Several architectures override module_alloc() only to define address range for code allocations different than VMALLOC address space. Provide a generic implementation in execmem that uses the parameters for address space ranges, required alignmen

[PATCH RESEND v8 03/16] nios2: define virtual address space for modules

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" nios2 uses kmalloc() to implement module_alloc() because CALL26/PCREL26 cannot reach all of vmalloc address space. Define module space as 32MiB below the kernel base and switch nios2 to use vmalloc for module allocations. Suggested-by: Thomas Gleix

[PATCH RESEND v8 06/16] mm: introduce execmem_alloc() and execmem_free()

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" module_alloc() is used everywhere as a mean to allocate memory for code. Beside being semantically wrong, this unnecessarily ties all subsystems that need to allocate code, such as ftrace, kprobes and BPF to modules and puts the burden of code

[PATCH RESEND v8 05/16] module: make module_memory_{alloc,free} more self-contained

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Move the logic related to the memory allocation and freeing into module_memory_alloc() and module_memory_free(). Signed-off-by: Mike Rapoport (IBM) Reviewed-by: Philippe Mathieu-Daudé --- kernel/module/main.c | 64 +++--

[PATCH RESEND v8 02/16] mips: module: rename MODULE_START to MODULES_VADDR

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" and MODULE_END to MODULES_END to match other architectures that define custom address space for modules. Signed-off-by: Mike Rapoport (IBM) --- arch/mips/include/asm/pgtable-64.h | 4 ++-- arch/mips/kernel/module.c | 4 ++-- arch/mips/

[PATCH RESEND v8 04/16] sparc: simplify module_alloc()

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Define MODULES_VADDR and MODULES_END as VMALLOC_START and VMALLOC_END for 32-bit and reduce module_alloc() to __vmalloc_node_range(size, 1, MODULES_VADDR, MODULES_END, ...) as with the new defines the allocations becomes identical for both 32 a

[PATCH RESEND v8 03/16] nios2: define virtual address space for modules

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" nios2 uses kmalloc() to implement module_alloc() because CALL26/PCREL26 cannot reach all of vmalloc address space. Define module space as 32MiB below the kernel base and switch nios2 to use vmalloc for module allocations. Suggested-by: Thomas Gleix

[PATCH RESEND v8 01/16] arm64: module: remove unneeded call to kasan_alloc_module_shadow()

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Since commit f6f37d9320a1 ("arm64: select KASAN_VMALLOC for SW/HW_TAGS modes") KASAN_VMALLOC is always enabled when KASAN is on. This means that allocations in module_alloc() will be tracked by KASAN protection for vmalloc() and that kasan

[PATCH RESEND v8 02/16] mips: module: rename MODULE_START to MODULES_VADDR

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" and MODULE_END to MODULES_END to match other architectures that define custom address space for modules. Signed-off-by: Mike Rapoport (IBM) --- arch/mips/include/asm/pgtable-64.h | 4 ++-- arch/mips/kernel/module.c | 4 ++-- arch/mips/

[PATCH RESEND v8 00/16] mm: jit/text allocator

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Hi, The patches are also available in git: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git/log/?h=execmem/v8 v8: * fix intialization of default_execmem_info v7: https://lore.kernel.org/all/20240429121620.1186447-1-r...@kernel.org * defi

[PATCH RESEND v8 01/16] arm64: module: remove unneeded call to kasan_alloc_module_shadow()

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Since commit f6f37d9320a1 ("arm64: select KASAN_VMALLOC for SW/HW_TAGS modes") KASAN_VMALLOC is always enabled when KASAN is on. This means that allocations in module_alloc() will be tracked by KASAN protection for vmalloc() and that kasan

[PATCH RESEND v8 00/16] mm: jit/text allocator

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Hi, The patches are also available in git: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git/log/?h=execmem/v8 v8: * fix intialization of default_execmem_info v7: https://lore.kernel.org/all/20240429121620.1186447-1-r...@kernel.org * defi

[PATCH v8 17/17] fixup: convert remaining archs: defaults handling

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Signed-off-by: Mike Rapoport (IBM) --- mm/execmem.c | 1 - 1 file changed, 1 deletion(-) diff --git a/mm/execmem.c b/mm/execmem.c index f6dc3fabc1ca..0c4b36bc6d10 100644 --- a/mm/execmem.c +++ b/mm/execmem.c @@ -118,7 +118,6 @@ static void __init __ex

[PATCH v8 16/17] bpf: remove CONFIG_BPF_JIT dependency on CONFIG_MODULES of

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" BPF just-in-time compiler depended on CONFIG_MODULES because it used module_alloc() to allocate memory for the generated code. Since code allocations are now implemented with execmem, drop dependency of CONFIG_BPF_JIT on CONFIG_MODULES and make

[PATCH v8 15/17] kprobes: remove dependency on CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" kprobes depended on CONFIG_MODULES because it has to allocate memory for code. Since code allocations are now implemented with execmem, kprobes can be enabled in non-modular kernels. Add #ifdef CONFIG_MODULE guards for the code dealing with kprobes insi

[PATCH v8 14/17] powerpc: use CONFIG_EXECMEM instead of CONFIG_MODULES where appropriate

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" There are places where CONFIG_MODULES guards the code that depends on memory allocation being done with module_alloc(). Replace CONFIG_MODULES with CONFIG_EXECMEM in such places. Signed-off-by: Mike Rapoport (IBM) --- arch/powerpc/Kconfig

[PATCH v8 13/17] x86/ftrace: enable dynamic ftrace without CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Dynamic ftrace must allocate memory for code and this was impossible without CONFIG_MODULES. With execmem separated from the modules code, execmem_text_alloc() is available regardless of CONFIG_MODULES. Remove dependency of dynamic ftrace on CONFIG_MODULE

[PATCH v8 12/17] arch: make execmem setup available regardless of CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" execmem does not depend on modules, on the contrary modules use execmem. To make execmem available when CONFIG_MODULES=n, for instance for kprobes, split execmem_params initialization out from arch/*/kernel/module.c and compile it when CONFIG_EXECMEM=y

[PATCH v8 11/17] powerpc: extend execmem_params for kprobes allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" powerpc overrides kprobes::alloc_insn_page() to remove writable permissions when STRICT_MODULE_RWX is on. Add definition of EXECMEM_KRPOBES to execmem_params to allow using the generic kprobes::alloc_insn_page() with the desired permissions. As po

[PATCH v8 10/17] arm64: extend execmem_info for generated code allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" The memory allocations for kprobes and BPF on arm64 can be placed anywhere in vmalloc address space and currently this is implemented with overrides of alloc_insn_page() and bpf_jit_alloc_exec() in arm64. Define EXECMEM_KPROBES and EXECMEM_BPF range

[PATCH v8 17/17] fixup: convert remaining archs: defaults handling

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Signed-off-by: Mike Rapoport (IBM) --- mm/execmem.c | 1 - 1 file changed, 1 deletion(-) diff --git a/mm/execmem.c b/mm/execmem.c index f6dc3fabc1ca..0c4b36bc6d10 100644 --- a/mm/execmem.c +++ b/mm/execmem.c @@ -118,7 +118,6 @@ static void __init __ex

[PATCH v8 09/17] riscv: extend execmem_params for generated code allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" The memory allocations for kprobes and BPF on RISC-V are not placed in the modules area and these custom allocations are implemented with overrides of alloc_insn_page() and bpf_jit_alloc_exec(). Define MODULES_VADDR and MODULES_END as VMALLOC_START and V

[PATCH v8 16/17] bpf: remove CONFIG_BPF_JIT dependency on CONFIG_MODULES of

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" BPF just-in-time compiler depended on CONFIG_MODULES because it used module_alloc() to allocate memory for the generated code. Since code allocations are now implemented with execmem, drop dependency of CONFIG_BPF_JIT on CONFIG_MODULES and make

[PATCH v8 15/17] kprobes: remove dependency on CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" kprobes depended on CONFIG_MODULES because it has to allocate memory for code. Since code allocations are now implemented with execmem, kprobes can be enabled in non-modular kernels. Add #ifdef CONFIG_MODULE guards for the code dealing with kprobes insi

[PATCH v8 08/17] mm/execmem, arch: convert remaining overrides of module_alloc to execmem

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Extend execmem parameters to accommodate more complex overrides of module_alloc() by architectures. This includes specification of a fallback range required by arm, arm64 and powerpc, EXECMEM_MODULE_DATA type required by powerpc, support for allocatio

[PATCH v8 14/17] powerpc: use CONFIG_EXECMEM instead of CONFIG_MODULES where appropriate

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" There are places where CONFIG_MODULES guards the code that depends on memory allocation being done with module_alloc(). Replace CONFIG_MODULES with CONFIG_EXECMEM in such places. Signed-off-by: Mike Rapoport (IBM) --- arch/powerpc/Kconfig

[PATCH v8 13/17] x86/ftrace: enable dynamic ftrace without CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Dynamic ftrace must allocate memory for code and this was impossible without CONFIG_MODULES. With execmem separated from the modules code, execmem_text_alloc() is available regardless of CONFIG_MODULES. Remove dependency of dynamic ftrace on CONFIG_MODULE

[PATCH v8 07/17] mm/execmem, arch: convert simple overrides of module_alloc to execmem

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Several architectures override module_alloc() only to define address range for code allocations different than VMALLOC address space. Provide a generic implementation in execmem that uses the parameters for address space ranges, required alignmen

[PATCH v8 12/17] arch: make execmem setup available regardless of CONFIG_MODULES

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" execmem does not depend on modules, on the contrary modules use execmem. To make execmem available when CONFIG_MODULES=n, for instance for kprobes, split execmem_params initialization out from arch/*/kernel/module.c and compile it when CONFIG_EXECMEM=y

[PATCH v8 11/17] powerpc: extend execmem_params for kprobes allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" powerpc overrides kprobes::alloc_insn_page() to remove writable permissions when STRICT_MODULE_RWX is on. Add definition of EXECMEM_KRPOBES to execmem_params to allow using the generic kprobes::alloc_insn_page() with the desired permissions. As po

[PATCH v8 06/17] mm: introduce execmem_alloc() and execmem_free()

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" module_alloc() is used everywhere as a mean to allocate memory for code. Beside being semantically wrong, this unnecessarily ties all subsystems that need to allocate code, such as ftrace, kprobes and BPF to modules and puts the burden of code

[PATCH v8 10/17] arm64: extend execmem_info for generated code allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" The memory allocations for kprobes and BPF on arm64 can be placed anywhere in vmalloc address space and currently this is implemented with overrides of alloc_insn_page() and bpf_jit_alloc_exec() in arm64. Define EXECMEM_KPROBES and EXECMEM_BPF range

[PATCH v8 05/17] module: make module_memory_{alloc,free} more self-contained

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" Move the logic related to the memory allocation and freeing into module_memory_alloc() and module_memory_free(). Signed-off-by: Mike Rapoport (IBM) Reviewed-by: Philippe Mathieu-Daudé --- kernel/module/main.c | 64 +++--

[PATCH v8 09/17] riscv: extend execmem_params for generated code allocations

2024-05-05 Thread Mike Rapoport
From: "Mike Rapoport (IBM)" The memory allocations for kprobes and BPF on RISC-V are not placed in the modules area and these custom allocations are implemented with overrides of alloc_insn_page() and bpf_jit_alloc_exec(). Define MODULES_VADDR and MODULES_END as VMALLOC_START and V

  1   2   3   4   5   6   7   8   9   10   >