Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Package: src:linux Version: 4.19.235-1 Severity: critical Tags: upstream Justification: breaks the whole system A recent upstream “stable” upgrade backported the removal of the qdisc_destroy() function (which, in itself, is questionable enough already and caused no small amount of fun) using qdisc_put() instead. However, qdisc_put() does not accept NULL pointers, causing oopses in several qdiscs that can be configured on a system. This breaks sudo (su works), networking and even deconfiguration is not possible, only /proc/sysrq-trigger makes it possible to recover. https://www.mail-archive.com/netdev@vger.kernel.org/msg314288.html fixes this but was not backported along. -- Package-specific info: ** Version: Linux version 4.19.0-20-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.235-1 (2022-03-17) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-20-amd64 root=/dev/vda2 ro net.ifnames=0 nomodeset ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: QEMU product_name: Standard PC (i440FX + PIIX, 1996) product_version: pc-i440fx-2.8 chassis_vendor: QEMU chassis_version: pc-i440fx-2.8 bios_vendor: SeaBIOS bios_version: 1.14.0-2 ** Loaded modules: ipt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_counter nft_chain_nat_ipv4 nf_nat_ipv4 xt_addrtype nft_compat xt_conntrack x_tables nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc nf_tables devlink nfnetlink overlay nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc loop kvm_intel ttm kvm drm_kms_helper irqbypass virtio_rng joydev drm evdev rng_core virtio_balloon serio_raw pcspkr button qemu_fw_cfg ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb crypto_simd cryptd glue_helper aes_x86_64 hid_generic usbhid hid virtio_net net_failover failover virtio_blk ata_generic ata_piix uhci_hcd libata ehci_hcd usbcore psmouse usb_common virtio_pci virtio_ring i2c_piix4 crc32c_intel scsi_mod virtio floppy ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:04.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device [1af4:1001] Subsystem: Red Hat, Inc Virtio block device [1af4:0002] Physical Slot: 4 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:05.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon [1af4:1002] Subsystem: Red Hat, Inc Virtio memory balloon [1af4:0005] Physical Slot: 5 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:06.0 Unclassified device [00ff]: Red Hat, Inc Virtio RNG [1af4:1005] Subsystem: Red Hat, Inc Virtio RNG [1af4:0004] Physical Slot: 6 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:07.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device [1af4:1000] Subsystem: Red Hat, Inc Virtio network device [1af4:0001] Physical Slot: 7 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci ** USB devices: not available -- System Information: Debian Release: 10.12 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-20-amd64 (SMP w/3 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages linux-image-4.19.0-20-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Control: tag -1 moreinfo On Tuesday, 21 June 2022 08:10:54 CEST Thorsten Glaser wrote: > Package: src:linux > Version: 4.19.235-1 > Severity: critical > Tags: upstream > Justification: breaks the whole system > > A recent upstream “stable” upgrade backported the removal of the > qdisc_destroy() function (which, in itself, is questionable enough > already and caused no small amount of fun) using qdisc_put() instead. > > However, qdisc_put() does not accept NULL pointers, causing oopses > in several qdiscs that can be configured on a system. This breaks > sudo (su works), networking and even deconfiguration is not possible, > only /proc/sysrq-trigger makes it possible to recover. > > https://www.mail-archive.com/netdev@vger.kernel.org/msg314288.html > fixes this but was not backported along. https://lore.kernel.org/all/20190921063607.ga1083...@kroah.com/ is about the 4.19.75 release and that contains that change in commit 7a1bad565cebfbf6956f9bb36dba734a48fa31d4 titled "net_sched: let qdisc_put() accept NULL pointer" which actually modifies the qdisc_destroy function https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/net/sched/sch_generic.c?h=linux-4.19.y#n1004 OTOH, does indeed not have that NULL check. In commit 92833e8b5db6c209e9311ac8c6a44d3bf1856659, part of v4.19.221, titled "net: sched: rename qdisc_destroy() to qdisc_put()" wasn't actually a straight rename, but some code moved around into a new qdisc_put function, which doesn't have the NULL check. In Debian, the release before 4.19.235-1 was 4.19.232-1 which should also have this bug. The release before that was 4.19.208-1, which shouldn't. Can you verify that? So I'm inclined to think that 92833e8b5db6c209e9311ac8c6a44d3bf1856659 is the commit which brought the bug back. signature.asc Description: This is a digitally signed message part.
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
On dinsdag 21 juni 2022 11:49:26 CEST you wrote: > https://lore.kernel.org/all/20190921063607.ga1083...@kroah.com/ is about the > 4.19.75 release and that contains that change in commit > 7a1bad565cebfbf6956f9bb36dba734a48fa31d4 titled "net_sched: let qdisc_put() > accept NULL pointer" which actually modifies the qdisc_destroy function > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/net/sc > hed/sch_generic.c?h=linux-4.19.y#n1004 OTOH, does indeed not have that NULL > check. It's a bit 'above my paygrade', but if qdisk_put() can accept a NULL pointer then I'm curious whether that would be allowed for other functions in that file as well ... there are several having "struct Qdisc *qdisc" as (only) parameter, but only qdisk_put() checks for NULL. That is also true for the current 'master' branch ... signature.asc Description: This is a digitally signed message part.
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Control: tag -1 - moreinfo Diederik de Haas dixit: >In Debian, the release before 4.19.235-1 was 4.19.232-1 which should also have >this bug. The release before that was 4.19.208-1, which shouldn't. >Can you verify that? Not easily any more, but I know it worked some weeks ago, and I *think* I particularily remember 208 as working. But I do have a clone of linux on another box and so I can look at ↓ >So I'm inclined to think that 92833e8b5db6c209e9311ac8c6a44d3bf1856659 is >the commit which brought the bug back. Yes, definitely. The lines… if (!qdisc) return; … from near the beginning of the now-static qdisc_destroy must be moved to the beginning of the new qdisc_put function. bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Diederik de Haas dixit: >It's a bit 'above my paygrade', but if qdisk_put() can accept a NULL pointer >then I'm curious whether that would be allowed for other functions in that file >as well ... there are several having "struct Qdisc *qdisc" as (only) >parameter, but only qdisk_put() checks for NULL. >That is also true for the current 'master' branch ... AIUI the check was added because qdisc_destroy() could accept one, and several qdiscs are using that, it’s like free(3) in that regard, the other functions aren’t. bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Control: tag -1 help On Tuesday, 21 June 2022 13:35:09 CEST Thorsten Glaser wrote: > >So I'm inclined to think that 92833e8b5db6c209e9311ac8c6a44d3bf1856659 is > >the commit which brought the bug back. > > Yes, definitely. The lines… > > if (!qdisc) > return; > > … from near the beginning of the now-static qdisc_destroy must > be moved to the beginning of the new qdisc_put function. Agreed. That would make it in line with 'master' and 'linux-5.10.y'. In branch 'linux-4.9.y' there is no qdisc_put function, so the above check seems rightly in qdisc_destroy there. This should be reported upstream, but I don't know what the best cq appropriate way to do that, so I'm referring that to the actual Debian maintainers, hence the 'help' tag. signature.asc Description: This is a digitally signed message part.
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Diederik de Haas dixit: >In branch 'linux-4.9.y' there is no qdisc_put function, so the above check >seems rightly in qdisc_destroy there. Not any more. Since… $ git tag --contains 92833e8b5db6 v4.19.221 […] … qdisc_destroy was renamed to qdisc_put in 4.19, breaking modules (grr). So yes, this needs to also be fixed upstream (hence me including that tag when reporbugging), but perhaps Debian can quickfix. bye, //mirabilos -- 16:47⎜«mika:#grml» .oO(mira ist einfach gut) 23:22⎜«mikap:#grml» mirabilos: und dein bootloader ist geil :)23:29⎜«mikap:#grml» und ich finds saugeil dass ich ein bsd zum booten mit grml hab, das muss ich dann gleich mal auf usb-stick installieren -- Michael Prokop über MirOS bsd4grml
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
On Tuesday, 21 June 2022 15:34:12 CEST Thorsten Glaser wrote: > >In branch 'linux-4.9.y' there is no qdisc_put function, so the above check > >seems rightly in qdisc_destroy there. I'm talking here about 4.9, not 4.19 ... > Not any more. Since… > > $ git tag --contains 92833e8b5db6 > v4.19.221 > […] Thanks for that command :-) I usually went through several manual steps to figure out in which release(s) a certain commit was. This is much quicker! > … qdisc_destroy was renamed to qdisc_put in 4.19, breaking modules (grr). And yes, it is broken in the 4.19 series since 4.19.221 (And not in 5.10 or upstream 'master') > So yes, this needs to also be fixed upstream (hence me including that tag > when reporbugging), but perhaps Debian can quickfix. What I have observed so far is that a commit needs to be accepted upstream (but doesn't have to have gone through the whole 'chain of command') before a temporary patch is accepted to quickly fix it in Debian. But as said before, I'm going to leave it up to the maintainers on the best way to go about fixing this issue. Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Diederik de Haas dixit: >I'm talking here about 4.9, not 4.19 ... Ah sorry, I can’t keep them distinguished in my head apparently, or it’s too hot… >> $ git tag --contains 92833e8b5db6 >> v4.19.221 >> […] > >Thanks for that command :-) I usually went through several manual steps to >figure out in which release(s) a certain commit was. This is much quicker! There is also git branch --contains. HTH ☺ >But as said before, I'm going to leave it up to the maintainers on the best >way to go about fixing this issue. Right. bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
On Tuesday, 21 June 2022 16:11:42 CEST Diederik de Haas wrote: > > So yes, this needs to also be fixed upstream (hence me including that tag > > when reporbugging), but perhaps Debian can quickfix. > > What I have observed so far is that a commit needs to be accepted upstream > (but doesn't have to have gone through the whole 'chain of command') before > a temporary patch is accepted to quickly fix it in Debian. I made an initial attempt at a patch, see attachment. https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2 describes a way to test whether this patch fixes the issue. (Just in case. I'm reasonably sure you already know this)>From 38cc721ef0c6745d808718d212968a173b6732b5 Mon Sep 17 00:00:00 2001 From: Diederik de Haas Date: Wed, 22 Jun 2022 11:44:05 +0200 Subject: [PATCH] [linux-4.19.y] net_sched: let qdisc_put() accept NULL pointer In commit 92833e8b5db6c209e9311ac8c6a44d3bf1856659 titled "net: sched: rename qdisc_destroy() to qdisc_put()" part of the functionality of qdisc_destroy() was moved into a (for linux-4.19.y) new function qdisk_put(), and the previous calls to qdisc_destroy() were changed to qdisk_put(). This made it similar to f.e. 5.10.y and current master. There was one part of qdisc_destroy() not moved over to qdisc_put() and that was the check for a NULL value, causing oopses. (See upstream commit: 6efb971ba8edfbd80b666f29de12882852f095ae) This patch fixes that. Fixes: 92833e8b5db6c209e9311ac8c6a44d3bf1856659 Reported-by: Thorsten Glaser Link: https://bugs.debian.org/1013299 --- net/sched/sch_generic.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c index 7c1b1eff84f4..cad2586c3473 100644 --- a/net/sched/sch_generic.c +++ b/net/sched/sch_generic.c @@ -970,8 +970,6 @@ static void qdisc_destroy(struct Qdisc *qdisc) const struct Qdisc_ops *ops; struct sk_buff *skb, *tmp; - if (!qdisc) - return; ops = qdisc->ops; #ifdef CONFIG_NET_SCHED @@ -1003,6 +1001,9 @@ static void qdisc_destroy(struct Qdisc *qdisc) void qdisc_put(struct Qdisc *qdisc) { + if (!qdisc) + return; + if (qdisc->flags & TCQ_F_BUILTIN || !refcount_dec_and_test(&qdisc->refcnt)) return; -- 2.36.1 signature.asc Description: This is a digitally signed message part.
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Control: tag -1 patch Control: tag -1 - help On Wed, 2022-06-22 at 11:47 +0200, Diederik de Haas wrote: > On Tuesday, 21 June 2022 16:11:42 CEST Diederik de Haas wrote: > > > So yes, this needs to also be fixed upstream (hence me including that tag > > > when reporbugging), but perhaps Debian can quickfix. > > > > What I have observed so far is that a commit needs to be accepted upstream > > (but doesn't have to have gone through the whole 'chain of command') before > > a temporary patch is accepted to quickly fix it in Debian. > > I made an initial attempt at a patch, see attachment. > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2 > describes a way to test whether this patch fixes the issue. > (Just in case. I'm reasonably sure you already know this) Looks good to me. Can you send it on to sta...@vger.kernel.org? You'll need to add your Signed-off-by. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
On Wednesday, 29 June 2022 15:24:45 CEST Ben Hutchings wrote: > Control: tag -1 patch > Control: tag -1 - help > > On Wed, 2022-06-22 at 11:47 +0200, Diederik de Haas wrote: > > On Tuesday, 21 June 2022 16:11:42 CEST Diederik de Haas wrote: > > > > So yes, this needs to also be fixed upstream (hence me including that > > > > tag when reporbugging), but perhaps Debian can quickfix. > > > > > > What I have observed so far is that a commit needs to be accepted > > > upstream > > > (but doesn't have to have gone through the whole 'chain of command') > > > before a temporary patch is accepted to quickly fix it in Debian. > > > > I made an initial attempt at a patch, see attachment. > > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html# > > s4.2.2 describes a way to test whether this patch fixes the issue. > > (Just in case. I'm reasonably sure you already know this) > > Looks good to me. Can you send it on to sta...@vger.kernel.org? > You'll need to add your Signed-off-by. I proposed my patch to expedite things and (much) prefer that Thorsten would send it (that's why I explicitly omitted the Signed-off-by statement). If there are follow up questions, they would also be directed to the person who found the issue and is the right person to answer them. I'd have to relay them and possibly introduce noise in the communication. I can do it, but I would like Thorsten to test the patch and confirm it actually does fix it. Having a Tested-By tag would be nice. When submitting a MR to the Debian kernel, I'm rightfully expected to have verified it does what it is supposed to do. For the upstream kernel, I'd expect the same at a minimum. Is the prefix I used for the patch, the correct one? signature.asc Description: This is a digitally signed message part.
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Diederik de Haas dixit: >I proposed my patch to expedite things and (much) prefer that Thorsten would I’m not the author… >I can do it, but I would like Thorsten to test the patch and confirm it It’s obviously correct, it moves the nil check to the correct place. I tested “the reverse” by doing… @@ -1275,11 +1275,12 @@ static void htb_destroy_class(struct Qdisc *sch, struct htb_class *cl) WARN_ON(!cl->leaf.q); #if (LINUX_VERSION_CODE < KERNEL_VERSION(4, 20, 0)) && \ (!defined(JENS_LINUX_4_19_SL) || (JENS_LINUX_4_19_SL < 221)) qdisc_destroy(cl->leaf.q); #else - qdisc_put(cl->leaf.q); + if (cl->leaf.q) + qdisc_put(cl->leaf.q); #endif } gen_kill_estimator(&cl->rate_est); tcf_block_put(cl->block); kfree(cl); … so the net effect is tested. bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
On Wed, 2022-06-29 at 16:49 +0200, Diederik de Haas wrote: > On Wednesday, 29 June 2022 15:24:45 CEST Ben Hutchings wrote: > > Control: tag -1 patch > > Control: tag -1 - help > > > > On Wed, 2022-06-22 at 11:47 +0200, Diederik de Haas wrote: > > > On Tuesday, 21 June 2022 16:11:42 CEST Diederik de Haas wrote: > > > > > So yes, this needs to also be fixed upstream (hence me including that > > > > > tag when reporbugging), but perhaps Debian can quickfix. > > > > > > > > What I have observed so far is that a commit needs to be accepted > > > > upstream > > > > (but doesn't have to have gone through the whole 'chain of command') > > > > before a temporary patch is accepted to quickly fix it in Debian. > > > > > > I made an initial attempt at a patch, see attachment. > > > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html# > > > s4.2.2 describes a way to test whether this patch fixes the issue. > > > (Just in case. I'm reasonably sure you already know this) > > > > Looks good to me. Can you send it on to sta...@vger.kernel.org? > > You'll need to add your Signed-off-by. > > I proposed my patch to expedite things and (much) prefer that Thorsten would > send it (that's why I explicitly omitted the Signed-off-by statement). > If there are follow up questions, they would also be directed to the person > who found the issue and is the right person to answer them. I'd have to relay > them and possibly introduce noise in the communication. As Thorsten's email is in the Reported-by pseudo-header, he should be cc'd on all discussions. > I can do it, but I would like Thorsten to test the patch and confirm it > actually does fix it. Having a Tested-By tag would be nice. > When submitting a MR to the Debian kernel, I'm rightfully expected to have > verified it does what it is supposed to do. For the upstream kernel, I'd > expect > the same at a minimum. > > Is the prefix I used for the patch, the correct one? "net/sched" seems to be preferred. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Control: forwarded -1 https://lore.kernel.org/all/20220629224938.7760-1-didi.deb...@cknow.org/ On Wednesday, 29 June 2022 15:24:45 CEST Ben Hutchings wrote: > Looks good to me. Can you send it on to sta...@vger.kernel.org? > You'll need to add your Signed-off-by. Done. signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Processing control commands: > tag -1 moreinfo Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport Added tag(s) moreinfo. -- 1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Processing control commands: > tag -1 - moreinfo Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport Removed tag(s) moreinfo. -- 1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Processing control commands: > tag -1 help Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport Added tag(s) help. -- 1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Processing control commands: > tag -1 patch Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport Added tag(s) patch. > tag -1 - help Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport Removed tag(s) help. -- 1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport
Processing control commands: > forwarded -1 > https://lore.kernel.org/all/20220629224938.7760-1-didi.deb...@cknow.org/ Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport Set Bug forwarded-to-address to 'https://lore.kernel.org/all/20220629224938.7760-1-didi.deb...@cknow.org/'. -- 1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems