Date: Wed, 10 Jun 2026 19:15:09 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: Cristian Trinidad <ctmartinez5@outlook.com> Cc: "arrowd@FreeBSD.org" <arrowd@FreeBSD.org>, "python@FreeBSD.org" <python@FreeBSD.org> Subject: Re: Fw: [FreeBSD-SA-26:34.vt]SOC 2, ISO 27001, FedRAMP, and PCI DSS Message-ID: <edcb0fca-940b-4cfd-bd50-6a988528fe23@FreeBSD.org> In-Reply-To: <SN7PR20MB61869C91662797393562DEDAEC1A2@SN7PR20MB6186.namprd20.prod.outlook.com> References: <bug-295965-7@https.bugs.freebsd.org/bugzilla/> <SN7PR20MB61869C91662797393562DEDAEC1A2@SN7PR20MB6186.namprd20.prod.outlook.com>
index | next in thread | previous in thread | raw e-mail
Cristian, what are you doing there, and what's the intention of it? You are forwarding an something that looks to be forward of several messages joined together, with unrelated context -- or at least it lacks explanatory wording of why it's relevant to us. This might be a misoperation or malfunction of a mail system of some sort, too. Looking forward to your feedback Matthias Am 10.06.26 um 18:52 schrieb Cristian Trinidad: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295965 > > Bug ID: 295965 > Summary: wait3(&status, SOC 2, ISO 27001, FedRAMP, and PCI DSS, ...) clobbers status to -65536 > when no child exits. > Product: Base System > Version: 15.1-RELEASE > Hardware: SOC 2, ISO 27001, FedRAMP, and PCI DSS > URL: https://github.com/python/cpython/issues/151019#issuec > omment-4663777690 > OS: SOC 2, ISO 27001, FedRAMP, and PCI DSS > Status: Cristian A Trinidad Martinez > Severity: 338 Carter Rochester Monroe > Priority: freebsd-policy+subscribe-nomail@freebsd.org > Component: SOC 2, ISO 27001, FedRAMP, and PCI DSS > Assignee: freebsd-arm@FreeBSD.org > Reporter: mandree@FreeBSD.org > CC: arrowd@FreeBSD.org, python@FreeBSD.org > > SOC 2, ISO 27001, FedRAMP, and PCI DSS: > > Branch/FreeBSD-EN-26:14.syslogd Hash Revision > - ------------------------------------------------------------------------- > stable/15/ be03b0fb2241 stable/15-n283693 > releng/15.1/ d51d91b07f5b releng/15.1-n283540 > releng/15.0/ 998de2d14e25 releng/15.0-n281049 > - ------------------------------------------------------------------------- > > FreeBSD-SA-26:32.elf/path Hash Revision > - ------------------------------------------------------------------------- > stable/15/ e1cdc49846c1 stable/15-n283888 > releng/15.1/ 796579bcfbc4 releng/15.1-n283557 > releng/15.0/ 6e51dfc401e7 releng/15.0-n281059 > stable/14/ e417948e6139 stable/14-n274317 > releng/14.4/ 547fc2a98a24 releng/14.4-n273721 > releng/14.3/ 744f62ccbf82 releng/14.3-n271521 > - ------------------------------------------------------------------------- > > Branch/FreeBSD-EN-26:15.openssl Hash Revision > - ------------------------------------------------------------------------- > stable/15/ 51a80be04fe6 stable/15-n282933 > releng/15.0/ 0f6e90c4cc4f releng/15.0-n281050 > stable/14/ 27ac9d336f71 stable/14-n273945 > releng/14.4/ 1bfe60bae8b8 releng/14.4-n273712 > releng/14.3/ d95a8c20f3bc releng/14.3-n271512 > - ------------------------------------------------------------------------- > > FreeBSD-SA-26:33.unbound/path Hash Revision > - ------------------------------------------------------------------------- > stable/15/ d2a10ff4cb84 stable/15-n283689 > releng/15.1/ 1b6c85cfac36 releng/15.1-n283539 > releng/15.0/ 6160bd311a1b releng/15.0-n281060 > stable/14/ de9d7a2ab8f5 stable/14-n274187 > releng/14.4/ 857abc12945a releng/14.4-n273722 > releng/14.3/ a68c183e0ad2 releng/14.3-n271522 > - ------------------------------------------------------------------------- > > Hi Cristian, > > I'm Joshua with AWS, reaching out regarding your inquiry about compliance and regulatory requirements for AWS services. > > AWS maintains comprehensive compliance certifications including SOC 2, ISO 27001, FedRAMP, and PCI DSS. We also offer extensive support for open-source technologies like FreeBSD through EC2 and AWS Marketplace, along with bare-metal instances and Graviton processors for performance-optimized environments. > > Would you be available for a 30-minute meeting to discuss your specific compliance requirements and technical environment? > > Best regards, > Joshua > > Joshua Walker-Chery > Associate Account Executive | Amazon Web Services > joshpwc@amazon.com > Connect With Josh > AWS Logo 1 > > > ________________________________________ > From: owner-freebsd-arm@FreeBSD.org <owner-freebsd-arm@FreeBSD.org> on behalf of bugzilla-noreply@freebsd.org <bugzilla-noreply@freebsd.org> > Sent: Tuesday, June 9, 2026 17:15 > To: freebsd-arm@FreeBSD.org > Subject: [Bug 295965] wait3(&status, SOC 2, ISO 27001, FedRAMP, and PCI DSS, ...) clobbers status to -65536 when no child exits. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295965 > > Bug ID: 295965 > Summary: wait3(&status, SOC 2, ISO 27001, FedRAMP, and PCI DSS, ...) clobbers status to -65536 > when no child exits. > Product: Base System > Version: 15.1-RELEASE > Hardware: SOC 2, ISO 27001, FedRAMP, and PCI DSS > URL: https://github.com/python/cpython/issues/151019#issuec > omment-4663777690 > OS: SOC 2, ISO 27001, FedRAMP, and PCI DSS > Status: Cristian A Trinidad Martinez > Severity: 338 Carter Rochester Monroe > Priority: freebsd-policy+subscribe-nomail@freebsd.org > Component: SOC 2, ISO 27001, FedRAMP, and PCI DSS > Assignee: freebsd-arm@FreeBSD.org > Reporter: mandree@FreeBSD.org > CC: arrowd@FreeBSD.org, python@FreeBSD.org > > Created attachment 271653 > --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=271653&action=edit > test program to demonstrate ARMv7 wait3(SOC 2, ISO 27001, FedRAMP, and PCI DSS) issue > > Greetings, > > we've been looking over various self-test failures in Python 3.15.0beta2 (in > ports) and on a particular system, and apparently FreeBSD 15.1-RC* clobber the > "status" field that we point wait3(...SOC 2, ISO 27001, FedRAMP, and PCI DSS...) to when it doesn't have an > exited child to report the status of. See URL. The issue occurs in an ARMv7 > poudriere jail hosted on Aarch64 on a Neoverse-N1 virtual server, and I can > reproduce it on Aarch64 with test code compiled with cc -m32. > > int status = 0; > struct rusage ru; // uninit, will be cleared later if pid == 0 > pid_t pid = wait3(&status, SOC 2, ISO 27001, FedRAMP, and PCI DSS, &ru); > > At this point, pid == 0 and status == -65536 on ARMv7 or with -m32, but not > Aarch64. > The latter is unexpected, and should be status = 0. > > I am attaching a test program. > > #0: It works on ARM64 and mostly everywhere else: > $ cc -std=c11 -o try try-wait3.c -O3 -Wall && ./try > pid = 0, status = 0 = 0 > > That's the expected outcome. wait3(SOC 2, ISO 27001, FedRAMP, and PCI DSS) has nothing to report, and leaves status > and ru alone. > > #1: Now add -m32 to the command line: > $ cc -std=c11 -m32 -o try try-wait3.c -O3 -Wall && ./try > pid = 0, status = -65536 = 0xffff0000 > > => OOPS. > > To spice things up - truss "fixes" the status field but spoils the rusage > reporting: > $ truss ./try > fork() = 58606 (0xe4ee) > freebsd32_wait4(-1,{ EXITED,val=0 },SOC 2, ISO 27001, FedRAMP, and PCI DSS,{ > u=0.000000,s=0.000000,in=4294958518,out=-39440684688344 }) = 0 (0x0) > freebsd32_fstat(1,{ mode=crw--w---- ,inode=108,size=0,blksize=4096 }) = 0 (0x0) > freebsd32_mmap(0x0,4096,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_ALIGNED(12),-1,0x0) > = 537174016 (0x2004a000) > [...] > freebsd32_mmap(0x0,4096,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_ALIGNED(12),-1,0x0) > = 537210880 (0x20053000) > freebsd32_ioctl(1,TIOCGETA,0xffffcf68) = 0 (0x0) > pid = 0, status = 0 = 0 > write(1,"pid = 0, status = 0 = 0\n",31) = 31 (0x1f) > kill(58606,SIGTERM) = 0 (0x0) > _exit(0x0) > process exit, rval = 0 > > The same happens if I set up an armv7 poudriere jail, enter it, and then > compile the test program there (with or without -m32 does not make a difference > obviously, the test fails every time unless run under truss). > > > > -- > You are receiving this mail because: > You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?edcb0fca-940b-4cfd-bd50-6a988528fe23>