Re: virtio_balloon regression in 5.19-rc3

2022-06-26 Thread Jason Wang 
On Fri, Jun 24, 2022 at 5:14 PM Michael S. Tsirkin  wrote:
>
> On Tue, Jun 21, 2022 at 06:10:00PM +0200, Ben Hutchings wrote:
> > On Tue, 2022-06-21 at 17:34 +0800, Jason Wang wrote:
> > > On Tue, Jun 21, 2022 at 5:24 PM David Hildenbrand  
> > > wrote:
> > > >
> > > > On 20.06.22 20:49, Ben Hutchings wrote:
> > > > > I've tested a 5.19-rc3 kernel on top of QEMU/KVM with machine type
> > > > > pc-q35-5.2.  It has a virtio balloon device defined in libvirt as:
> > > > >
> > > > > 
> > > > >> > > > function="0x0"/>
> > > > > 
> > > > >
> > > > > but the virtio_balloon driver fails to bind to it:
> > > > >
> > > > > virtio_balloon virtio4: init_vqs: add stat_vq failed
> > > > > virtio_balloon: probe of virtio4 failed with error -5
> > > > >
> > > >
> > > > Hmm, I don't see any recent changes to drivers/virtio/virtio_balloon.c
> > > >
> > > > virtqueue_add_outbuf() fails with -EIO if I'm not wrong. That's the
> > > > first call of virtqueue_add_outbuf() when virtio_balloon initializes.
> > > >
> > > >
> > > > Maybe something in generic virtio code changed?
> > >
> > > Yes, we introduced the IRQ hardening. That could be the root cause and
> > > we've received lots of reports so we decide to disable it by default.
> > >
> > > Ben, could you please try this patch: (and make sure
> > > CONFIG_VIRTIO_HARDEN_NOTIFICATION is not set)
> > >
> > > https://lore.kernel.org/lkml/20220620024158.2505-1-jasow...@redhat.com/T/
> >
> > Yes, that patch fixes the regression for me.
> >
> > Ben.
>
>
> Jason are you going to fix balloon to call device_ready before
> registering device with linux?

I'm working on the fix, (spot various bugs during review).

Thanks

> > --
> > Ben Hutchings
> > Any smoothly functioning technology is indistinguishable
> > from a rigged demo.
>
>

Bug#1013895: RTL8188EUS 802.11n Wireless Network Adapter not working on 5.18

2022-06-26 Thread Santiago Ruano Rincón 
Package: src:linux
Version: 5.18.5-1
Severity: important

Dear linux maintainers,

Not sure if this should be filed against firmware-realtek, and sorry if
that is the case. I have a WiFi USB dongle that doesn't work on linux
5.18, but it does work on 5.15.

You can see this error in the logs below during boot, or when I replug
the dongle:

 r8188eu 1-1.2:1.0: _rtw_init_xmit_priv failed

Maybe this is relevant:
https://lkml.org/lkml/2022/5/21/527

Thanks for your work,

 -- Santiago


lsusb -d 0bda:8179 -v:

Couldn't open device, some information will be missing

Bus 001 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n 
Wireless Network Adapter
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x0bda Realtek Semiconductor Corp.
  idProduct  0x8179 RTL8188EUS 802.11n Wireless Network Adapter
  bcdDevice0.00
  iManufacturer   1 Realtek
  iProduct2 802.11n NIC
  iSerial 3 00E04C0001
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x0027
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03  EP 3 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0


-- Package-specific info:
** Version:
Linux version 5.18.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 
11.3.0-3) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.50.20220615) #1 SMP 
PREEMPT_DYNAMIC Debian 5.18.5-1 (2022-06-16)

** Command line:
BOOT_IMAGE=/vmlinuz-5.18.0-2-amd64 root=/dev/mapper/nomada--vg-root ro quiet

** Tainted: C (1024)
 * staging driver was loaded

** Kernel log:
[   65.967972] sr 1:0:0:0: Attached scsi generic sg1 type 5
[   66.200182] input: PC Speaker as /devices/platform/pcspkr/input/input9
[   66.205789] at24 0-0050: supply vcc not found, using dummy regulator
[   66.211386] iTCO_vendor_support: vendor-support=0
[   66.220396] at24 0-0050: 256 byte spd EEPROM, read-only
[   66.262644] EXT4-fs (sda1): mounting ext2 file system using the ext4 
subsystem
[   66.264240] EXT4-fs (sda1): mounted filesystem without journal. Quota mode: 
none.
[   66.264268] ext2 filesystem being mounted at /boot supports timestamps until 
2038 (0x7fff)
[   66.334031] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 163840 ms 
ovfl timer
[   66.334038] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules
[   66.334040] RAPL PMU: hw unit of domain package 2^-16 Joules
[   66.334042] RAPL PMU: hw unit of domain pp1-gpu 2^-16 Joules
[   66.359000] iTCO_wdt iTCO_wdt.1.auto: Found a Panther Point TCO device 
(Version=2, TCOBASE=0x0460)
[   66.359986] iTCO_wdt iTCO_wdt.1.auto: initialized. heartbeat=30 sec 
(nowayout=0)
[   66.360743] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.4)
[   66.373820] dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI SMBIOS 
userspace interface not supported(0), try upgrading to a newer BIOS
[   66.406003] ACPI: AC: AC Adapter [AC] (off-line)
[   66.519073] audit: type=1400 audit(1656278514.058:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=574 
comm="apparmor_parser"
[   66.524501] audit: type=1400 audit(1656278514.062:3): apparmor="

Re: Please update non-free firmware to the latest version

2022-06-26 Thread David Liu 
Dear Maintainer,

It has been a while, Is there any update on this package? Please consider 
packaging it in Debian, It will support more new hardware, Thanks!

Best Regards,
David Liu

发件人: David Liu
发送时间: 2022年5月22日 14:08
收件人: sub...@bugs.debian.org
主题: Please update non-free firmware to the latest version

Package: firmware-linux-nonfree
Version: 20210818-1

Hello,
I have noticed the firmware-linux-nonfree has been no update since 20210818, in 
Linux Kernel git the latest release is 20220509 
(https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/), 
Please update it, Thanks.

Best Regards

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

2022-06-26 Thread Daniel Lewart 
Ben, et al,

On Mon, 13 Jun 2022 18:23:18 +0200 Ben Hutchings  wrote:

> Since the truncated signatures are in the source packages, this is a
> problem introduced by the code signing service and will need to be
> fixed there.

Assuming that the code-signing service uses the kernel's scripts/sign-file
and calls PKCS7_sign() ...

Which version of OpenSSL/libssl is used?

Are kernel build logs available for download or viewing?

Thank you!
Dan
Urbana, Illinois

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

2022-06-26 Thread Daniel Lewart 
Ben, et al,

BH> I wrote a script to check for short signatures (and other unexpected
BH> things) in detached signature files:
BH> 
https://salsa.debian.org/kernel-team/kernel-team/-/blob/master/scripts/benh/check-sig-params

DL> I tried running your script, but it generates an error (see below).
DL> What am I doing wrong?

I was running it for the kernel module instead of the detached signature.  D'oh!

This works:
$ extract-module-sig.pl -s
/lib/modules/5.10.0-15-amd64/kernel/net/netfilter/xt_l2tp.ko
2>/dev/null | check-sig-params /dev/stdin

Sorry for the noise,
Dan
Urbana, Illinois

Processed: nfs-common: retitle 1013868

2022-06-26 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 1013868 nfs-common: Move Python scripts to separate package
Bug #1013868 [nfs-common] nfs-common: Split between Python scripts to separate 
package
Changed Bug title to 'nfs-common: Move Python scripts to separate package' from 
'nfs-common: Split between Python scripts to separate package'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013868: nfs-common: Split between Python scripts to separate package

2022-06-26 Thread Gioele Barabucci 



Package: nfs-common
Version: 1:2.6.1-2

Dear maintainers of nfs-common,

could you please move the three Python scripts included in nfs-common to 
a separate -extras package?


Currently nfs-common Depends on `python3` and, on lean/containerized 
client systems, it is the only package that requires it. For this 
reason, in 2019 Fedora moved the scripts `mountstats`, `nfsiostat` and 
`nfsconvert` to a separate package [1,2], required on servers (for 
`nfsconver`) but not on clients.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1667889
[2] https://github.com/coreos/fedora-coreos-tracker/issues/121

Kind regards,

--
Gioele Barabucci