[Ubuntu-ha] [Bug 1862947] Re: crmsh should be taken back to -main
This bug was fixed in the package pacemaker - 2.0.1-5ubuntu5 --- pacemaker (2.0.1-5ubuntu5) focal; urgency=medium * Fix: Last attempt i386 binary packages removal was wrong (-Nlibkate) * Ubuntu i386 binary compatibility only effort: (LP: #1863437) - i386 binary package removal: - pacemaker - pacemaker-cli-utils - pacemaker-remote - pacemaker-resource-agents -- Rafael David Tinoco Sat, 15 Feb 2020 18:52:20 + ** Changed in: pacemaker (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1862947 Title: crmsh should be taken back to -main Status in crmsh package in Ubuntu: Fix Released Status in pacemaker package in Ubuntu: Fix Released Status in crmsh source package in Focal: Fix Released Status in pacemaker source package in Focal: Fix Released Bug description: crmsh is currently the most tested cluster resource manager configuration tool we have for Ubuntu (pcs being the second one, and already scheduled for more tests in order to replace it in a near future). With that said, currently crmsh is found at -universe: rafaeldtinoco@workstation:~$ rmadison crmsh crmsh | 1.2.5+hg1034-1ubuntu3 | trusty | source, all crmsh | 1.2.5+hg1034-1ubuntu4 | trusty-updates | source, all crmsh | 2.2.0-1 | xenial | source, ... crmsh | 3.0.1-3ubuntu1| bionic/universe | source, all crmsh | 3.0.1-3ubuntu1| disco/universe | source, all crmsh | 4.1.0-2ubuntu2| eoan/universe | source, all crmsh | 4.2.0-2ubuntu1| focal/universe | source, all When it should be placed back in main since there is no other way to configure pacemaker other than editing manually - blergh - a CIB file for example. There's gotta to be supported way (-main) to configure clustering. There was already a MIR for crmsh: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1205019 So I'm including crmsh as a pacemaker dependency for it to be triggered as a component mismatch. This will likely be enough after some IRC discussions with other Ubuntu developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1862947/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1863437] Re: [focal] pacemaker i386 should drop a few i386 only packages
This bug was fixed in the package pacemaker - 2.0.1-5ubuntu5 --- pacemaker (2.0.1-5ubuntu5) focal; urgency=medium * Fix: Last attempt i386 binary packages removal was wrong (-Nlibkate) * Ubuntu i386 binary compatibility only effort: (LP: #1863437) - i386 binary package removal: - pacemaker - pacemaker-cli-utils - pacemaker-remote - pacemaker-resource-agents -- Rafael David Tinoco Sat, 15 Feb 2020 18:52:20 + ** Changed in: pacemaker (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1863437 Title: [focal] pacemaker i386 should drop a few i386 only packages Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Focal: Fix Released Bug description: When executing pacemaker i386 autopkgtests I realized that package "resource-agents" wasn't available for i386. When discussing this with @vorlon we came into the conclusion that some i386 only cluster packages could be removed from the repository, towards the effort of having *only the essential* packages available in i386 (to be run together with an amd64 host). IRC log: """ resource-agents i386 binary package the pacemaker binary is /not/ present on i386 in the release pocket that may have been an overly aggressive removal vorlon: are u keeping pacemaker because of dependencies ? yeah, I removed it when I shouldn't have (https://launchpad.net/ubuntu/focal/i386/pacemaker) rafaeldtinoco: pacemaker-dev is a build-dep of something else we need, see the referenced germinate output for full details https://people.canonical.com/~ubuntu-archive/germinate- output/i386.focal/i386+build-depends pacemaker-dev is a build-dep of dlm and libesmtp-dev is a build-dep of pacemaker, not the other way around (and dlm is a build-dep of lvm2) ah gotcha dlm -> corosync -> pacemaker so, even though I removed the binary in error from the release pocket, the right answer is still for pacemaker/i386 binary to go away (leaving only the -dev and lib packages) do you want me to fix that up, or do you want to? to fix that we should do like we did to samba ? yeah looks like the binaries you'll need to drop are pacemaker, pacemaker-cli-utils, pacemaker-remote and I'll remove those from -proposed right now, so that those don't hold up migration but I'll hold off on adding the hint until they're dropped from the source deal, and next hint ill do with proper branch """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1863437/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1863677] [NEW] fence_scsi needs lvm2 package so it should depend on it
Public bug reported:
Playing with fence_scsi I have noticed that one of my images did not
have lvm2 package installed. With that, the following error ocurred:
$ sudo fence_scsi -n clufocal03 --action=status
2020-02-17 19:57:02,324 ERROR: Unable to run /sbin/vgs --noheadings --separator
: --sort pv_uuid --options vg_attr,pv_name --config 'global { locking_type = 0
} devices { preferred_names = [ "^/dev/dm" ] }'
when trying to scsi fence one of my nodes.
fence-agents should depend and/or suggest all packages it depends on for
the correct execution of provided agents.
** Affects: fence-agents (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: fence-agents (Ubuntu)
Status: New => Confirmed
** Changed in: fence-agents (Ubuntu)
Importance: Undecided => Medium
** Changed in: fence-agents (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1863677
Title:
fence_scsi needs lvm2 package so it should depend on it
Status in fence-agents package in Ubuntu:
Confirmed
Bug description:
Playing with fence_scsi I have noticed that one of my images did not
have lvm2 package installed. With that, the following error ocurred:
$ sudo fence_scsi -n clufocal03 --action=status
2020-02-17 19:57:02,324 ERROR: Unable to run /sbin/vgs --noheadings
--separator : --sort pv_uuid --options vg_attr,pv_name --config 'global {
locking_type = 0 } devices { preferred_names = [ "^/dev/dm" ] }'
when trying to scsi fence one of my nodes.
fence-agents should depend and/or suggest all packages it depends on
for the correct execution of provided agents.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1863677/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1863677] [NEW] fence_scsi needs lvm2 package so it should depend on it
You have been subscribed to a public bug by Rafael David Tinoco (rafaeldtinoco):
Playing with fence_scsi I have noticed that one of my images did not
have lvm2 package installed. With that, the following error ocurred:
$ sudo fence_scsi -n clufocal03 --action=status
2020-02-17 19:57:02,324 ERROR: Unable to run /sbin/vgs --noheadings --separator
: --sort pv_uuid --options vg_attr,pv_name --config 'global { locking_type = 0
} devices { preferred_names = [ "^/dev/dm" ] }'
when trying to scsi fence one of my nodes.
fence-agents should depend and/or suggest all packages it depends on for
the correct execution of provided agents.
** Affects: fence-agents (Ubuntu)
Importance: Undecided
Status: New
--
fence_scsi needs lvm2 package so it should depend on it
https://bugs.launchpad.net/bugs/1863677
You received this bug notification because you are a member of Ubuntu High
Availability Team, which is subscribed to the bug report.
___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1863437] Re: [focal] pacemaker i386 should drop a few i386 only packages
https://salsa.debian.org/ha-team/pacemaker/merge_requests/1 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1863437 Title: [focal] pacemaker i386 should drop a few i386 only packages Status in pacemaker package in Ubuntu: In Progress Status in pacemaker source package in Focal: In Progress Bug description: When executing pacemaker i386 autopkgtests I realized that package "resource-agents" wasn't available for i386. When discussing this with @vorlon we came into the conclusion that some i386 only cluster packages could be removed from the repository, towards the effort of having *only the essential* packages available in i386 (to be run together with an amd64 host). IRC log: """ resource-agents i386 binary package the pacemaker binary is /not/ present on i386 in the release pocket that may have been an overly aggressive removal vorlon: are u keeping pacemaker because of dependencies ? yeah, I removed it when I shouldn't have (https://launchpad.net/ubuntu/focal/i386/pacemaker) rafaeldtinoco: pacemaker-dev is a build-dep of something else we need, see the referenced germinate output for full details https://people.canonical.com/~ubuntu-archive/germinate- output/i386.focal/i386+build-depends pacemaker-dev is a build-dep of dlm and libesmtp-dev is a build-dep of pacemaker, not the other way around (and dlm is a build-dep of lvm2) ah gotcha dlm -> corosync -> pacemaker so, even though I removed the binary in error from the release pocket, the right answer is still for pacemaker/i386 binary to go away (leaving only the -dev and lib packages) do you want me to fix that up, or do you want to? to fix that we should do like we did to samba ? yeah looks like the binaries you'll need to drop are pacemaker, pacemaker-cli-utils, pacemaker-remote and I'll remove those from -proposed right now, so that those don't hold up migration but I'll hold off on adding the hint until they're dropped from the source deal, and next hint ill do with proper branch """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1863437/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1863437] Re: [focal] pacemaker i386 should drop a few i386 only packages
Upstream already had the following commit (since @vorlon opened the bug
in January):
commit 543574f18
Author: Ferenc Wágner
Date: Thu Jan 9 14:19:19 2020
Omit pacemaker{, -cli-utils, -remote} on Ubuntu/i386
Closes: #948379
diff --git a/debian/rules b/debian/rules
index 1d186d741..04acd7da2 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,8 +11,14 @@ export DEB_LDFLAGS_MAINT_APPEND=-Wl,-z,defs
# Avoid useless dependencies in the utilities
export DEB_LDFLAGS_MAINT_APPEND+=-Wl,--as-needed
+# Ubuntu/i386 shrank into a compatibility layer not carrying the
+# dependencies of some of our binary packages (#948379):
+ifeq ($(shell dpkg-vendor --query vendor)/$(DEB_HOST_ARCH), Ubuntu/i386)
+UBUNTU_EXCLUDES = -Npacemaker -Npacemaker-cli-utils -Npacemaker-remote
+endif
+
%:
- dh $@ --with python3
+ dh $@ --with python3 $(UBUNTU_EXCLUDES)
# autoreconf options taken from autogen.sh
# without symlink usage (-s) to make --as-needed effective
I'll propose it to include: -Npacemaeker-resource-agents and we will be
good.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948379
** Bug watch added: Debian Bug tracker #948379
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948379
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1863437
Title:
[focal] pacemaker i386 should drop a few i386 only packages
Status in pacemaker package in Ubuntu:
In Progress
Status in pacemaker source package in Focal:
In Progress
Bug description:
When executing pacemaker i386 autopkgtests I realized that package
"resource-agents" wasn't available for i386. When discussing this with
@vorlon we came into the conclusion that some i386 only cluster
packages could be removed from the repository, towards the effort of
having *only the essential* packages available in i386 (to be run
together with an amd64 host).
IRC log:
"""
resource-agents i386 binary package
the pacemaker binary is /not/ present on i386 in the release pocket
that may have been an overly aggressive removal
vorlon: are u keeping pacemaker because of dependencies ?
yeah, I removed it when I shouldn't have
(https://launchpad.net/ubuntu/focal/i386/pacemaker)
rafaeldtinoco: pacemaker-dev is a build-dep of something else we
need,
see the referenced germinate output for full details
https://people.canonical.com/~ubuntu-archive/germinate-
output/i386.focal/i386+build-depends
pacemaker-dev is a build-dep of dlm
and libesmtp-dev is a build-dep of pacemaker, not the other way
around
(and dlm is a build-dep of lvm2)
ah gotcha
dlm -> corosync -> pacemaker
so, even though I removed the binary in error from the release
pocket,
the right answer is still for pacemaker/i386 binary to go away (leaving only
the
-dev and lib packages)
do you want me to fix that up, or do you want to?
to fix that we should do like we did to samba ?
yeah
looks like the binaries you'll need to drop are pacemaker,
pacemaker-cli-utils, pacemaker-remote
and I'll remove those from -proposed right now, so that those don't
hold up migration
but I'll hold off on adding the hint until they're dropped from the
source
deal, and next hint ill do with proper branch
"""
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1863437/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1855140] Re: How to handle tmpfiles.d in non-systemd environments
> From my understanding this means that supporting an alternative init
system is optional ("Packages may include support for alternate init
systems besides systemd"). So basically this is up to the package
maintainer whether or not the package should support an alternative init
system.
I'm not sure that the Docker use case was intended to be within the
scope of the Debian GR. But nevertheless, I think that in Debian it's
still up to package maintainers to decide to what extent to support the
Docker use case as it always has been. The Debian GR was relevant in
that it didn't end up mandating an alternative to tmpfiles.d for example
which might have affected any technical solution to this general
problem.
For Ubuntu, I think it makes sense to support it and to send Debian
package maintainers patches as appropriate.
The question is: how, technically, can we resolve this particular issue?
I think it would be best if it could be done centrally somehow, rather
than tweaking each affected package individually. Could the systemd
tmpfiles.d mechanism somehow be used by Docker image builds as a
machine-readable list of temporary directories to arrange to be handled
automatically? If so, then that one solution could fix this entire class
of problem.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1855140
Title:
How to handle tmpfiles.d in non-systemd environments
Status in haproxy package in Ubuntu:
Opinion
Status in systemd package in Ubuntu:
New
Bug description:
This is a general issue about systemd features like tmpfiles.d which
won't run in some environments like docker containers.
Packages more and more rely on that with haproxy being the example
that opened the bug, but clearly not the only one.
I wanted to add tasks for all affected, but a qucik check showed that
there are almost to many.
$ apt-file search tmpfiles.d | cut -d':' -f 1 | sort | uniq
129 at the moment and probably increasing.
List of affected as of Dec 2019:
acmetool anytun apt-cacher-ng bacula-common bind9 binkd bley bzflag-server
ceph-common certmonger cockpit-ws colord connman courier-authdaemon
courier-imap courier-ldap courier-mlm courier-mta courier-pop cryptsetup-bin
cyrus-common dbus dhcpcanon diaspora-common dnssec-trigger ejabberd fail2ban
firebird3.0-server freeipa-client freeipa-server glusterfs-server gvfs-common
haproxy hddemux heartbeat htcondor i2pd inn inspircd iodine knot knot-resolver
krb5-otp laptop-mode-tools lemonldap-ng-fastcgi-server libreswan lighttpd lirc
lvm2 mailman mailman3 mailman3-web man-db mandos memcached mon mpd munge
munin-common myproxy-server nagios-nrpe-server ngircd nrpe-ng nscd nsd
nullmailer nut-client nut-server opencryptoki opendkim opendmarc
opendnssec-enforcer opendnssec-signer opennebula opennebula-sunstone opensips
open-vm-tools-desktop openvpn passwd pesign php7.2-fpm pidentd ploop
postgresql-common prads prelude-correlator prelude-lml prelude-manager puppet
pushpin resource-agents rkt rpcbind rsyslog samba-common-bin screen
shairport-sync shibboleth-sp2-utils slurmctld slurmd slurmdbd sogo
spice-vdagent sqwebmail sslh sudo sudo-ldap systemd systemd-container tcpcryptd
tinyproxy tuned ulogd2 uptimed vrfydmn vsftpd w1retap-doc wdm
wesnoth-1.12-server x2goserver-common xpra yadifa zabbix-agent
zabbix-java-gateway zabbix-proxy-mysql zabbix-proxy-pgsql zabbix-proxy-sqlite3
zabbix-server-mysql zabbix-server-pgsql
Handling of these heavily Depends on the recent Debian GR [1].
I'd suggest we wait how that turns out and then need to consider how
(if?) to handle it in a central place, probably systemd or a
derivative tool as started to be discussed in [2]
If possible I'd avoid fixes in individual packages as it encourages
growth of various workarounds for a problem that needs a general
solution.
[1]: https://www.debian.org/vote/2019/vote_002
[2]: https://lists.debian.org/debian-devel/2019/12/msg00060.html
--- Original report below ---
When installing the haproxy package from the current Ubuntu 18.04
Bionic repos, the package does not install the directory /run/haproxy.
This directory is mentioned in the default config file
/etc/haproxy/haproxy.cfg:
stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd
listeners
Starting HAProxy manually will show the following error:
# /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg
[ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket
[/run/haproxy/admin.sock]
After manual creation of the directory, the start works:
# mkdir /run/haproxy
# /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg
# ps auxf
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash
root32 0.0 0.0 34400 2900 pts/0R+ 15:45
[Ubuntu-ha] [Bug 1863437] Re: [focal] pacemaker i386 should drop a few i386 only packages
Merged and uploaded. -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1863437 Title: [focal] pacemaker i386 should drop a few i386 only packages Status in pacemaker package in Ubuntu: In Progress Status in pacemaker source package in Focal: In Progress Bug description: When executing pacemaker i386 autopkgtests I realized that package "resource-agents" wasn't available for i386. When discussing this with @vorlon we came into the conclusion that some i386 only cluster packages could be removed from the repository, towards the effort of having *only the essential* packages available in i386 (to be run together with an amd64 host). IRC log: """ resource-agents i386 binary package the pacemaker binary is /not/ present on i386 in the release pocket that may have been an overly aggressive removal vorlon: are u keeping pacemaker because of dependencies ? yeah, I removed it when I shouldn't have (https://launchpad.net/ubuntu/focal/i386/pacemaker) rafaeldtinoco: pacemaker-dev is a build-dep of something else we need, see the referenced germinate output for full details https://people.canonical.com/~ubuntu-archive/germinate- output/i386.focal/i386+build-depends pacemaker-dev is a build-dep of dlm and libesmtp-dev is a build-dep of pacemaker, not the other way around (and dlm is a build-dep of lvm2) ah gotcha dlm -> corosync -> pacemaker so, even though I removed the binary in error from the release pocket, the right answer is still for pacemaker/i386 binary to go away (leaving only the -dev and lib packages) do you want me to fix that up, or do you want to? to fix that we should do like we did to samba ? yeah looks like the binaries you'll need to drop are pacemaker, pacemaker-cli-utils, pacemaker-remote and I'll remove those from -proposed right now, so that those don't hold up migration but I'll hold off on adding the hint until they're dropped from the source deal, and next hint ill do with proper branch """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1863437/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 1852122] Re: ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12)
This bug was fixed in the package linux - 5.3.0-40.32 --- linux (5.3.0-40.32) eoan; urgency=medium * eoan/linux: 5.3.0-40.32 -proposed tracker (LP: #1861214) * No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after modprobe sof (LP: #1860248) - ASoC: SOF: Intel: fix HDA codec driver probe with multiple controllers * ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12) (LP: #1852122) - ocfs2: fix the crash due to call ocfs2_get_dlm_debug once less * QAT drivers for C3XXX and C62X not included as modules (LP: #1845959) - [Config] CRYPTO_DEV_QAT_C3XXX=m, CRYPTO_DEV_QAT_C62X=m and CRYPTO_DEV_QAT_DH895xCC=m * Eoan update: upstream stable patchset 2020-01-24 (LP: #1860816) - scsi: lpfc: Fix discovery failures when target device connectivity bounces - scsi: mpt3sas: Fix clear pending bit in ioctl status - scsi: lpfc: Fix locking on mailbox command completion - Input: atmel_mxt_ts - disable IRQ across suspend - f2fs: fix to update time in lazytime mode - iommu: rockchip: Free domain on .domain_free - iommu/tegra-smmu: Fix page tables in > 4 GiB memory - dmaengine: xilinx_dma: Clear desc_pendingcount in xilinx_dma_reset - scsi: target: compare full CHAP_A Algorithm strings - scsi: lpfc: Fix SLI3 hba in loop mode not discovering devices - scsi: csiostor: Don't enable IRQs too early - scsi: hisi_sas: Replace in_softirq() check in hisi_sas_task_exec() - powerpc/pseries: Mark accumulate_stolen_time() as notrace - powerpc/pseries: Don't fail hash page table insert for bolted mapping - powerpc/tools: Don't quote $objdump in scripts - dma-debug: add a schedule point in debug_dma_dump_mappings() - leds: lm3692x: Handle failure to probe the regulator - clocksource/drivers/asm9260: Add a check for of_clk_get - clocksource/drivers/timer-of: Use unique device name instead of timer - powerpc/security/book3s64: Report L1TF status in sysfs - powerpc/book3s64/hash: Add cond_resched to avoid soft lockup warning - ext4: update direct I/O read lock pattern for IOCB_NOWAIT - ext4: iomap that extends beyond EOF should be marked dirty - jbd2: Fix statistics for the number of logged blocks - scsi: tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and WRITE(6) - scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow - f2fs: fix to update dir's i_pino during cross_rename - clk: qcom: Allow constant ratio freq tables for rcg - clk: clk-gpio: propagate rate change to parent - irqchip/irq-bcm7038-l1: Enable parent IRQ if necessary - irqchip: ingenic: Error out if IRQ domain creation failed - fs/quota: handle overflows of sysctl fs.quota.* and report as unsigned long - scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences - PCI: rpaphp: Fix up pointer to first drc-info entry - scsi: ufs: fix potential bug which ends in system hang - powerpc/pseries/cmm: Implement release() function for sysfs device - PCI: rpaphp: Don't rely on firmware feature to imply drc-info support - PCI: rpaphp: Annotate and correctly byte swap DRC properties - PCI: rpaphp: Correctly match ibm, my-drc-index to drc-name when using drc- info - powerpc/security: Fix wrong message when RFI Flush is disable - scsi: atari_scsi: sun3_scsi: Set sg_tablesize to 1 instead of SG_NONE - clk: pxa: fix one of the pxa RTC clocks - bcache: at least try to shrink 1 node in bch_mca_scan() - HID: quirks: Add quirk for HP MSU1465 PIXART OEM mouse - HID: logitech-hidpp: Silence intermittent get_battery_capacity errors - ARM: 8937/1: spectre-v2: remove Brahma-B53 from hardening - libnvdimm/btt: fix variable 'rc' set but not used - HID: Improve Windows Precision Touchpad detection. - HID: rmi: Check that the RMI_STARTED bit is set before unregistering the RMI transport device - watchdog: Fix the race between the release of watchdog_core_data and cdev - scsi: pm80xx: Fix for SATA device discovery - scsi: ufs: Fix error handing during hibern8 enter - scsi: scsi_debug: num_tgts must be >= 0 - scsi: NCR5380: Add disconnect_mask module parameter - scsi: iscsi: Don't send data to unbound connection - scsi: target: iscsi: Wait for all commands to finish before freeing a session - gpio: mpc8xxx: Don't overwrite default irq_set_type callback - apparmor: fix unsigned len comparison with less than zero - scripts/kallsyms: fix definitely-lost memory leak - powerpc: Don't add -mabi= flags when building with Clang - cdrom: respect device capabilities during opening action - perf script: Fix brstackinsn for AUXTRACE - perf regs: Make perf_reg_name() return "unknown" instead of NULL - s390/zcrypt: handle new reply code FILTERED_BY_HYPERVISOR - libfdt: define INT32_MAX and UINT32_MAX in libfdt_env.h -
