Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #78764 > unrolled thread
| Started by | Yoann Congal <yoann.congal@smile.fr> |
|---|---|
| First post | 2023-04-17 12:20 +0200 |
| Last post | 2023-05-15 12:50 +0200 |
| Articles | 6 — 3 participants |
Back to article view | Back to linux.debian.kernel
Bug#1034506: Request to enable CONFIG_HSR as module Yoann Congal <yoann.congal@smile.fr> - 2023-04-17 12:20 +0200
Bug#1034506: Request to enable CONFIG_HSR as module Salvatore Bonaccorso <carnil@debian.org> - 2023-04-19 09:00 +0200
Bug#1034506: Request to enable CONFIG_HSR as module Yoann Congal <yoann.congal@smile.fr> - 2023-04-19 09:50 +0200
Bug#1034506: Request to enable CONFIG_HSR as module Salvatore Bonaccorso <carnil@debian.org> - 2023-04-19 12:00 +0200
Bug#1034506: Request to enable CONFIG_HSR as module Yoann Congal <yoann.congal@smile.fr> - 2023-04-19 12:00 +0200
Bug#1034506: marked as done (Request to enable CONFIG_HSR as module) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-05-15 12:50 +0200
| From | Yoann Congal <yoann.congal@smile.fr> |
|---|---|
| Date | 2023-04-17 12:20 +0200 |
| Subject | Bug#1034506: Request to enable CONFIG_HSR as module |
| Message-ID | <Glu7L-2CbS-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Source: linux Severity: wishlist Tags: newcomer patch X-Debbugs-Cc: yoann.congal@smile.fr Hi maintainers, HSR (High-availability Seamless Redundancy) and PRP (Parallel Redundancy Protocol) are two network protocols used in environment where network node failure should not trigger a frame loss. Both provide seamless failover against this kind of failure. Both of these are enabled in kernel by CONFIG_HSR which is currently disabled. HSR and PRP are defined in IEC 62439-3:2016 and used in many industrial standards (in our case, IEC 61850 about connected systems in electrical substations) This module is handled by iproute2 since 5.10 (available in bullseye). I've already created a merge-request for this request : https://salsa.debian.org/kernel-team/linux/-/merge_requests/682 Thank you for considering this request. Best regards, -- System Information: Debian Release: 11.6 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-0.deb11.5-rt-amd64 (SMP w/24 CPU threads; PREEMPT) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
[toc] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2023-04-19 09:00 +0200 |
| Message-ID | <Gm9Xj-31Dl-3@gated-at.bofh.it> |
| In reply to | #78764 |
Hi Yoann, On Mon, Apr 17, 2023 at 12:12:50PM +0200, Yoann Congal wrote: > Source: linux > Severity: wishlist > Tags: newcomer patch > X-Debbugs-Cc: yoann.congal@smile.fr > > Hi maintainers, > > HSR (High-availability Seamless Redundancy) and PRP (Parallel Redundancy > Protocol) are two network protocols used in environment where network > node failure should not trigger a frame loss. Both provide seamless > failover against this kind of failure. > > Both of these are enabled in kernel by CONFIG_HSR which is currently > disabled. > > HSR and PRP are defined in IEC 62439-3:2016 and used in many industrial > standards (in our case, IEC 61850 about connected systems in electrical > substations) > > This module is handled by iproute2 since 5.10 (available in bullseye). > > I've already created a merge-request for this request : > https://salsa.debian.org/kernel-team/linux/-/merge_requests/682 > > Thank you for considering this request. Thanks for providing the merge request. Just for cross-reference and transparency: This change cannot go anymore for bookworm, but we can pick it up for trixie. Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | Yoann Congal <yoann.congal@smile.fr> |
|---|---|
| Date | 2023-04-19 09:50 +0200 |
| Message-ID | <GmaJH-327Z-1@gated-at.bofh.it> |
| In reply to | #78773 |
On 4/19/23 08:47, Salvatore Bonaccorso wrote: > Hi Yoann, Hi! > > Thanks for providing the merge request. Just for cross-reference and > transparency: This change cannot go anymore for bookworm, but we can > pick it up for trixie. Yeah, I understood that it won't go into bookworm as I was a bit late for that, but that's OK. AFAIK it will end up in backports so we could have bookworm + backported kernel with this module activated, or am I wrong? Thanks! -- Yoann Congal Smile ECS - Tech Expert
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2023-04-19 12:00 +0200 |
| Message-ID | <GmcLv-33gS-3@gated-at.bofh.it> |
| In reply to | #78774 |
Hi, On Wed, Apr 19, 2023 at 09:39:14AM +0200, Yoann Congal wrote: > On 4/19/23 08:47, Salvatore Bonaccorso wrote: > > Hi Yoann, > > Hi! > > > > > Thanks for providing the merge request. Just for cross-reference and > > transparency: This change cannot go anymore for bookworm, but we can > > pick it up for trixie. > > Yeah, I understood that it won't go into bookworm as I was a bit > late for that, but that's OK. > AFAIK it will end up in backports so we could have bookworm + > backported kernel with this module activated, or am I wrong? No that is correct assumption. Once bookworm-backports opens (and someone in the team picks it), the version from the upper suite can go into bookworm-backports, and that will have the same configuration basis, so include the activated module as well. So in short, correct. Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | Yoann Congal <yoann.congal@smile.fr> |
|---|---|
| Date | 2023-04-19 12:00 +0200 |
| Message-ID | <GmcLv-33gS-1@gated-at.bofh.it> |
| In reply to | #78764 |
On 4/19/23 11:46, Salvatore Bonaccorso wrote: > Hi, > > On Wed, Apr 19, 2023 at 09:39:14AM +0200, Yoann Congal wrote: >> On 4/19/23 08:47, Salvatore Bonaccorso wrote: >>> Hi Yoann, >> >> Hi! >> >>> >>> Thanks for providing the merge request. Just for cross-reference and >>> transparency: This change cannot go anymore for bookworm, but we can >>> pick it up for trixie. >> >> Yeah, I understood that it won't go into bookworm as I was a bit >> late for that, but that's OK. >> AFAIK it will end up in backports so we could have bookworm + >> backported kernel with this module activated, or am I wrong? > > No that is correct assumption. Once bookworm-backports opens (and > someone in the team picks it), the version from the upper suite can go > into bookworm-backports, and that will have the same configuration > basis, so include the activated module as well. > > So in short, correct. Awesome! Thanks! -- Yoann Congal Smile ECS - Tech Expert
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2023-05-15 12:50 +0200 |
| Subject | Bug#1034506: marked as done (Request to enable CONFIG_HSR as module) |
| Message-ID | <GvDW9-93yH-1@gated-at.bofh.it> |
| In reply to | #78764 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Mon, 15 May 2023 10:40:13 +0000 with message-id <E1pyVcj-007Ld0-3E@fasolo.debian.org> and subject line Bug#1034506: fixed in linux 6.3.2-1~exp1 has caused the Debian Bug report #1034506, regarding Request to enable CONFIG_HSR as module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1034506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034506 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web