search for: rwe

Hi, to get the residuals and coefficients I did the following: kurse <- read.table("kurse.txt" header=T) the data: index bmw mru rwe vow kar sie bas 1 159,70 74,18 338,21 89,03 110,30 141,23 178,53 67,97 2 160,76 73,46 343,66 89,38 110,30 142,66 180,45 68,30 3 162,45 74,18 349,12 91,54 108,54 146,22 183,12 68,85 4 162,18 72,74 349,12 92,20 106,43 144,80 181,75 68,52 5 161,64 72,98 340,93 91,43 101,87 144,08 181,41 68,...

...in the address space, e.g. Elf file type is EXEC (Executable file) Entry point 0x80001a0f There are 1 program headers, starting at offset 52 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x80000000 0x80000000 0x08284 0x08284 RWE 0x1000 Section to Segment mapping: Segment Sections... 00 .text .rodata .eh_frame .data However, what ldd does is different. (To create a single segment I use --omagic argument, it works fine and is unrelated). The first segment is created at a lower address, with ELF headers in it, an...

...urse[,-c(1)]) > y <- kurse$index > t(x) %*% x Error in t(x) %*% x : requires numeric matrix/vector arguments > x <- as.matrix(x) > xtxi <- solve(t(x) %*% x) Error in solve.default(t(x) %*% x) : singular matrix `a' in solve My data looks like this: index bmw mru rwe vow kar sie bas 1 159.70 74.18 338.21 89.03 110.30 141.23 178.53 67.97 2 160.76 73.46 343.66 89.38 110.30 142.66 180.45 68.30 3 162.45 74.18 349.12 91.54 108.54 146.22 183.12 68.85 4 162.18 72.74 349.12 92.20 106.43 144.80 181.75 68.52 5 161.64 72.98 340.93 91.43 101.87 144.08 181.4...

...does batch processing on the files using VB.NET code. There are many other regular users: "user1", "user2", etc... They are all part of the "users" group If "user1" opens up a file in Excel, it changes the ownership on the file and permissions to: User - rwe Group - rw- Other - --- The default setting is: User - rwe Group - rwe Other - --- I can live with the change of the permissions, but it also changes the ownership from "serveruser" to "user1". As part of my code, the server applies a "Normal" attribute t...

...does batch processing on the files using VB.NET code. There are many other regular users: "user1", "user2", etc... They are all part of the "users" group If "user1" opens up a file in Excel, it changes the ownership on the file and permissions to: User - rwe Group - rw- Other - --- The default setting is: User - rwe Group - rwe Other - --- I can live with the change of the permissions, but it also changes the ownership from "serveruser" to "user1". As part of my code, the server applies a "Normal" attrib...

...T (MAXPAGESIZE)); .AX : { *(.AX.*) } . = ALIGN(CONSTANT (MAXPAGESIZE)); .A : { *(.A.*) } .AW : { *(.AW.*) } } It will create single segment, combining access attributes: LOAD 0x0000000000200000 0x0000000000000000 0x0000000000000000 0x0000000000200010 0x0000000000200010 RWE 200000 So looks like its behavior is to combine all sections before writable ones to single segment and create writable segment for others if possible, but if not it will create single segment for everything. I think FreeBSD script relies on this behavior. When linking with ld It has 2 PT_LOADS...

Add a simple test which uses scanelf or readelf to detect whether the supermin executable is really not executable. Kind of followup of commit c9f7a7998021e1cbe22a8ec325d43e2bdc3eff5a. --- tests/Makefile.am | 1 + tests/test-execstack.sh | 32 ++++++++++++++++++++++++++++++++ 2 files changed, 33 insertions(+) create mode 100755 tests/test-execstack.sh diff --git a/tests/Makefile.am

...0000011a5e R E 200000 LOAD 0x0000000000011a60 0x0000000000411a60 0x0000000000411a60 0x0000000000000100 0x0000000000004288 RW 200000 GNU_STACK 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 RWE 8 Section to Segment mapping: Segment Sections... 00 .text .rodata 01 .data .bss 02 The .text and .rodata sections are placed in a segment starting at 0x200000, but .data and .bss are placed starting at 0x411a60. But binaries are linked starting at 0x400000 - theref...

Thanks for your ideas, Sean ! >The bug is not likely to be corrupted data in the decompressed output (that is just calling into a gzip routine or something). You shouldn't have to dump/printf->trace from memory during boot to see that data since the "real" kernel binary that is being decompressed into that memory region is probably already somewhere > in your build tree

...E" , "CS.PA" , "DAI.DE" , "ALV.DE" , "EOAN.DE" , "CA.PA" , "G.MI" , "DE" , "EXR.MI" , "MUV2.BE" , "UG.PA" , "PRU.L", "VOD.L" , "DPB.BE" , "REP.MC" , "RWE.BE" , "AGN.AS" , "FTE.PA" , "EAD" , "LGEN.L" , "CNP.PA" , "ULVR.L" , "TKA.BE" , "RIO.L" , "NOK" , "SGO.PA" , "RNO.PA" , "VIE.PA" , "BAYN.DE" , "SAN.PA" ,...

...4 --- a/arch/x86_64/kernel/vmlinux.lds.S +++ b/arch/x86_64/kernel/vmlinux.lds.S @@ -13,6 +13,12 @@ OUTPUT_FORMAT("elf64-x86-64", "elf64-x86 OUTPUT_ARCH(i386:x86-64) ENTRY(phys_startup_64) jiffies_64 = jiffies; +PHDRS { + text PT_LOAD FLAGS(5); /* R_E */ + data PT_LOAD FLAGS(7); /* RWE */ + user PT_LOAD FLAGS(7); /* RWE */ + note PT_NOTE FLAGS(4); /* R__ */ +} SECTIONS { . = __START_KERNEL; @@ -31,7 +37,7 @@ SECTIONS KPROBES_TEXT *(.fixup) *(.gnu.warning) - } = 0x9090 + } :text = 0x9090 /* out-of-line lock text */ .text.lock : AT(ADDR(.text.lock) - LOAD_OFFSE...

...quot;; + eol = ' '; + } + } + printf("\r%s: %s%s%c", filename_ptr, status, clear_eol, eol); + } + fclose(fp); + } while (*++argv); + printf("\r%d files OK, %d broken, %d not checked.%s\n", + good, tested - good, files - tested, clear_eol); + printf("\n\rWe are now paused. Read the above result. Press enter to finish.\n"); + break; + sleep(5); + return 0; +} -- -Ady

With latest kernel (Linus tree as of 5.6 merge window), I get the following warning in the kernel 'dmesg': [ 5.746588] process '/bin/sh' started with executable stack This comes from commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/exec.c?id=47a2ebb7f5053387f5753b524f4920b9b829f922 "execve: warn if process starts with executable

Hi, I hope I''m right here. If not then please point me in the right direction. My problem in short: I have problems using (pinning, mmu_update) physical pages from 0x900000 to 0xB1000 usualy. I''m writing my own little amd64 64bit toy kernel (based on Mini-OS as starting point) for xen and I run into problems with the way the start of day sets up the physical pages. My kernel

I re-wrote the compile script to build klibc (cleaning up how I do it, and how to find the source tarballs). It seems to be compiling fine. I tried several of the commands in usr/utils/static and most one. However, the sleep command fails in a strange way (EINVAL on execve): ================================================================ faraday/phil /home/phil/klibc-project-0 581> strace

On Wed, 24 Apr 2024, Hadley Wickham wrote: >> >> >> >>>>> That is not true at all - the presence of header does not constitute >>>> declaration of something as the R API. There are cases where internal >>>> functions are in the headers for historical or other reasons since the >>>> headers are used both for the internal

Hi Rusty, I had a look over your 011-paravirt-head.S.patch. I'm struggling to come up with a list of any benefits over having separate entrypoints for each hypervisor. Multiple entry pros: * allows maximum startup flexibility for any given hypervisor * for Xen at least, it's pretty simple * the "what hypervisor am I under" question is answered trivially cons:

xc_dom_alloc_page deals with virtual address not physical address. When an ELF is loaded, virtual address and physical address may be different. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/libxc/xc_dom_arm.c | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/tools/libxc/xc_dom_arm.c b/tools/libxc/xc_dom_arm.c index a40e04d..75a6f1c

[ REPOST: Apologies to anyone who has seen this before. It didn't make it onto any of the lists it should have. -J ] Hi Andrew, This series of patches lays the basic ground work for the paravirtualized kernel patches coming later on. I think this lot is ready for the rough-and-tumble world of the -mm tree. For the most part, these patches do nothing or very little. The patches should

[ REPOST: Apologies to anyone who has seen this before. It didn't make it onto any of the lists it should have. -J ] Hi Andrew, This series of patches lays the basic ground work for the paravirtualized kernel patches coming later on. I think this lot is ready for the rough-and-tumble world of the -mm tree. For the most part, these patches do nothing or very little. The patches should