On Wed, 2022-06-22 at 10:05 +0200, Graham Inggs wrote:
> Hi,
>
> As part of the interim architecture qualification for bookworm, we
> request that DSA, the security team, Wanna build, and the toolchain
> maintainers review and update their list of known concerns for bookworm
> release architecture
On Fri, Jul 15, 2022 at 01:51:21PM +0200, Ben Hutchings wrote:
>
> For i386, I have some concerns about upstream support of the Linux
> kernel. CPU security mitigations for x86 are concentrated on amd64,
> with i386 being left behind. Mitigation of Meltdown required a
> different implementation
On Wed, Jun 22, 2022 at 10:05:37AM +0200, Graham Inggs wrote:
>...
> List of concerns for architectures
> ==
>...
> * Concern for mips64el and mipsel: builders are extremely slow.
>(Raised by kernel team; carried over from bullseye)
>...
This was mitigated with
On Sat, 2022-07-16 at 06:23 +0300, Adrian Bunk wrote:
> On Fri, Jul 15, 2022 at 01:51:21PM +0200, Ben Hutchings wrote:
> >
> > For i386, I have some concerns about upstream support of the Linux
> > kernel. CPU security mitigations for x86 are concentrated on amd64,
> > with i386 being left behind
On Sat, Jul 16, 2022 at 03:54:21PM +0200, Ben Hutchings wrote:
> On Sat, 2022-07-16 at 06:23 +0300, Adrian Bunk wrote:
> > On Fri, Jul 15, 2022 at 01:51:21PM +0200, Ben Hutchings wrote:
>...
> > This is not limited to i386, it is also quite relevant for embedded arm
> > where new products using 32-
On Fri, Jul 15, 2022 at 7:51 AM Ben Hutchings wrote:
> On Wed, 2022-06-22 at 10:05 +0200, Graham Inggs wrote:
> > Hi,
> >
> > As part of the interim architecture qualification for bookworm, we
> > request that DSA, the security team, Wanna build, and the toolchain
> > maintainers review and updat
On Sat, 2022-07-16 at 11:20 -0400, Timothy M Butterworth wrote:
[...]
> i386 is anchient in tech terms it was introduced in 1985. If debian wants
> to keep supporting 32 bit OS then it should bump up to i686.
[...]
We did that years ago. We just didn't rename the architecture.
Ben.
--
Ben Hutc
On Sat, Jul 16, 2022 at 11:46 AM Ben Hutchings wrote:
> On Sat, 2022-07-16 at 11:20 -0400, Timothy M Butterworth wrote:
> [...]
> > i386 is anchient in tech terms it was introduced in 1985. If debian wants
> > to keep supporting 32 bit OS then it should bump up to i686.
> [...]
>
> We did that ye
On Sat, 2022-07-16 at 18:03 +0300, Adrian Bunk wrote:
> On Sat, Jul 16, 2022 at 03:54:21PM +0200, Ben Hutchings wrote:
> > On Sat, 2022-07-16 at 06:23 +0300, Adrian Bunk wrote:
> > > On Fri, Jul 15, 2022 at 01:51:21PM +0200, Ben Hutchings wrote:
> > ...
> > > This is not limited to i386, it is also
Am Wed, Jun 22, 2022 at 10:05:37AM +0200 schrieb Graham Inggs:
> Hi,
>
> As part of the interim architecture qualification for bookworm, we
> request that DSA, the security team, Wanna build, and the toolchain
> maintainers review and update their list of known concerns for bookworm
> release arch
On Sun, Jul 17, 2022 at 02:02:34PM +0200, Ben Hutchings wrote:
> On Sat, 2022-07-16 at 18:03 +0300, Adrian Bunk wrote:
>...
> > What problem is building i386 bookworm kernel binaries causing for you
> > that are not present on other architectures like armhf or s390x?
>
> Good question. I think t
On Sun, Jul 17, 2022 at 09:02:23PM +0200, Moritz Mühlenhoff wrote:
>...
> but the quickly vaninishing
> upstream support for i386 and the lack of active porters make i386
> problematic from the Security Team's point of view.
>
> For packages where new upstream releases are being introduced
> this m
12 matches
Mail list logo
