Re: git: 30780c3f584a - stable/13 - README.md: correct GPL expansion
On Fri, 17 Dec 2021 at 11:09, Mark Millard wrote: > > I'm confused, beyond just LGPL claims in the (fairly > current) source code, but GPL more generally: > > # grep -rl "SPDX.*GPL" /usr/main-src/ You need to exclude the ones with SPDX tags like: SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0 but also note that this text in README.md is just documenting the top-level gnu/ subdirectory.
Re: git: 30780c3f584a - stable/13 - README.md: correct GPL expansion
On Sat, Dec 18, 2021, 10:31 AM Ed Maste wrote: > On Fri, 17 Dec 2021 at 11:09, Mark Millard wrote: > > > > I'm confused, beyond just LGPL claims in the (fairly > > current) source code, but GPL more generally: > > > > # grep -rl "SPDX.*GPL" /usr/main-src/ > > You need to exclude the ones with SPDX tags like: > SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0 > > but also note that this text in README.md is just documenting the > top-level gnu/ subdirectory. > Yes. Readme.md has never been a comprehensive guide to license compliance. I'm working on revamping the project's license policies to be more in line with current industry practices. Warner >
Re: git: 30780c3f584a - stable/13 - README.md: correct GPL expansion
On 2021-Dec-18, at 09:30, Ed Maste wrote: > On Fri, 17 Dec 2021 at 11:09, Mark Millard wrote: >> >> I'm confused, beyond just LGPL claims in the (fairly >> current) source code, but GPL more generally: >> >> # grep -rl "SPDX.*GPL" /usr/main-src/ > > You need to exclude the ones with SPDX tags like: > SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0 > > but also note that this text in README.md is just documenting the > top-level gnu/ subdirectory. # grep -r "SPDX.*GPL" /usr/main-src/ | egrep -vi "(mit|bsd|Linux-OpenIB)" | grep -v sys/contrib/device-tree/ | more /usr/main-src/sys/gnu/gcov/gcc_4_7.c:// SPDX-License-Identifier: GPL-2.0 /usr/main-src/sys/gnu/gcov/gcov_fs.c:// SPDX-License-Identifier: GPL-2.0 /usr/main-src/sys/dts/include/dt-bindings/soc/qcom,tcsr.h:/* SPDX-License-Identifier: GPL-2.0 */ But . . . # grep -r "SPDX.*GPL" /usr/main-src/ | egrep -vi "(mit|bsd|Linux-OpenIB)" | grep sys/contrib/device-tree/ | wc 31049958 345089 === Mark Millard marklmi at yahoo.com
Re: git: 30780c3f584a - stable/13 - README.md: correct GPL expansion
On Sat, Dec 18, 2021 at 11:33 AM Mark Millard via freebsd-current < freebsd-curr...@freebsd.org> wrote: > On 2021-Dec-18, at 09:30, Ed Maste wrote: > > > On Fri, 17 Dec 2021 at 11:09, Mark Millard wrote: > >> > >> I'm confused, beyond just LGPL claims in the (fairly > >> current) source code, but GPL more generally: > >> > >> # grep -rl "SPDX.*GPL" /usr/main-src/ > > > > You need to exclude the ones with SPDX tags like: > > SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0 > > > > but also note that this text in README.md is just documenting the > > top-level gnu/ subdirectory. > > # grep -r "SPDX.*GPL" /usr/main-src/ | egrep -vi "(mit|bsd|Linux-OpenIB)" > | grep -v sys/contrib/device-tree/ | more > /usr/main-src/sys/gnu/gcov/gcc_4_7.c:// SPDX-License-Identifier: GPL-2.0 > /usr/main-src/sys/gnu/gcov/gcov_fs.c:// SPDX-License-Identifier: GPL-2.0 > /usr/main-src/sys/dts/include/dt-bindings/soc/qcom,tcsr.h:/* > SPDX-License-Identifier: GPL-2.0 */ > > But . . . > > # grep -r "SPDX.*GPL" /usr/main-src/ | egrep -vi "(mit|bsd|Linux-OpenIB)" > | grep sys/contrib/device-tree/ | wc > 31049958 345089 > Yea, that doesn't matter that much... Those are generally not used for tier 1 platforms, except for some arm64 boards. And when they are used, they create a separate work (the .dtb files). And that's even assuming these files are expressive enough to have enough creative content that a copyright could attach... It's not used at all the build kernels, userland, etc (though one does have an option to attach a dtb to a kernel, to be fair). And they are all well marked with SPDX tags, so we're not misrepresenting anything and the project's use of them is in full compliance with whichever GPL they are released under. Downstream users will, as with all license things, need to ensure their uses comply. There have been various statements about these files over the years which one should consult if one ships a system with the .dtb w/o the .dts sources to determine compliance measures necessary (though the standard GPL measures will work, some folks have disclaimed the need to do them for their .dts files, ymmv). Warner
Re: 12.3:[ZFS pointer corruption] kernel crash exporting FreeBSD src repo
On Mon, Dec 13, 2021 at 08:34:13PM +0100, Peter wrote: ! I have a filesystem with the FreeBSD src repo clone. ! ! When I do ! > git checkout-index -a --prefix=/new-filesystem/ ! in 5 of 6 cases I get a kernel crash. ! ! Fatal trap 12: page fault while in kernel mode ! cpuid = 19; apic id = 19 ! fault virtual address = 0x410 ! fault code = supervisor read data, page not present ! instruction pointer = 0x20:0x808e9815 ! stack pointer = 0x28:0xfe00e667bf50 ! frame pointer = 0x28:0xfe00e667bff0 ! code segment= base 0x0, limit 0xf, type 0x1b ! = DPL 0, pres 1, long 1, def32 0, gran 1 ! processor eflags= interrupt enabled, resume, IOPL = 0 ! current process = 18330 (git) ! trap number = 12 This one did finally turn out to be a known issue in the cam component. It had haunted me already back in 2016, and made me disassemble the whole machine, replace it with a newer (and then turning out to be much worse) machine with lots of other issues, and I couldn't figure what the problem actually is - it was not obvious when and why it had appeared and I thought it to be hardware related. Anyway, with another two changes to newer hardware (this time hopefully to the better) I thought the issue had disappeared. No, it hasn't - it just comes in a different disguise: now it creates bogus data in ZFS (back then the crashes appeared within the cam component). But the remedy/workaround is the same: changing the cam options. cheerio, PMc
