kernel news – 21.05.2012

-Guenter Roeck has hwmon fixes for -rc2:

This pull request adds two more patches to the request I sent out last week.
If there is a reason for not accepting it, I would appreciate if you would
let me know to give me a chance to correct it.

-Konrad Rzeszutek Wilk has xen-stable fixes for -rc1:

Fixes:
* Regression fix in xen privcmd fixing a memory leak.
* Add Documentation for tmem driver.
* Simplify and remove code in the tmem driver.
* Cleanups.

-John W. Linville has a wireless pull request:

This pull request is intended for the 3.10 series. It contains a
variety of fixes for problems discovered during the merge window and
after 3.10-rc1.

For the mac80211 bits, Johannes says the following:

“This is what I have:
* a patch from Felix to fix RCU usage in his rate table code
* a patch from Ilan to add the wdev id to some notifications so they can
actually be used by userspace
* Sasha Levin found an issue in how hwsim handles devices
* a fix for a bug in the wiphy_register() error path that’s been there forever
* three fixes for WoWLAN
* AP mode frame matching was erroneously giving frames to all virtual AP
interfaces (reported by Jouni)
* a fix for HT handling in my CSA changes, found by Sujith
* a fix for some locking simplifications gone wrong
* Ben Greear found more cfg80211/mac80211 state confusion
* and a fix for another bug found by Jouni: local state changes need to be
reported by mac80211 to cfg80211 so it disconnects properly.”

And for the iwlwifi bits, he says:

“I have fixes for a firmware crash during resume, multicast RX,
aggregation and a workaround for a firmware scanning bug.”

Along with those…

Albert Pool adds a USB ID to the rtl8192cu driver.

Arend van Spriel restores a driver option support flag that had been
removed from 3.9 due to a bug in that version of the driver.

Felix Fietkau fixes a trio of ath9k issues with a series of small
patches.

Geert Uytterhoeven provides a Kconfig fix for ath9k (which you also
merged, so it isn’t in the diff here).

Larry Finger gives us a fix for a build warning on big-endian systems
for rtlwifi.

Rafał Miłecki adds some core IDs to the bcma driver.

Sujith Manoharan fixes a module unloading crash in ath9k, and corrects
some calibration settings for AR9485.

-Linus Torvalds announces Linux kernel 3.10-rc2:

So it’s been just over a week, and -rc2 is out.

For being an -rc2, it’s not unreasonably sized, but I did take a few
pulls that I wouldn’t have taken later in the rc series. So it’s not
exactly small either. We’ve got arch updates (PPC, MIPS, PA-RISC),
we’ve got driver fixes (net, gpu, target, xen), and we’ve got
filesystem updates (btrfs, ext4 and cepth – rbd).

And various random small fixes. Shortlog appended, it should get
smaller and more readable going forward.

-Dave Airlie has radeon and nouveau DRM fixes:

This is just a set of nouveau and radeon fixes, the nouveau ones fix some
suspend/resume regressions since use of copy engines and some fixes for Z
compression on some newer chipsets.

I’ve got another pull request for some new AMD radeon hw that shouldn’t
touch any existing hw support that I’ll send after this, its based on this
one, so pulling it will get this + that.
###########################################################################
Since I know its outside the merge window, but since this is new hw I
thought I’d try and provoke the new hw exception, it just fills in the
blanks in the driver for the new AMD sun and hainan chipsets. The pull is
based on the previous one with the changelog just for the new pieces.

-Steven Rostedt announces the release of kernel 3.6.11.4, here is the patch:

https://www.kernel.org/pub/linux/kernel/projects/rt/3.6/stable/patch-3.6.11.4.xz.

-Martin Schwidefsky has s390 updates, and that’s about it for today.

kernel news – 16.05.2013

-Thomas Gleixner has core, perf, timer and x86 fixes:

* Two fixlets for the fallout of the generic idle task conversion
* Documentation update
##################################################################
* Cure for not using zalloc in the first place, which leads to
random crashes with CPUMASK_OFF_STACK.

* Revert a user space visible change which broke udev

* Add a missing cpu_online early return introduced by the new
full dyntick conversions

* Plug a long standing race in the timer wheel cpu hotplug
code. Sigh…

* Cleanup NOHZ per cpu data on cpu down to prevent stale data
on cpu up.
####################################################################
* Fix for a task exit cleanup race caused by a missing a preempt
disable

* Cleanup of the event notification functions with a massive
reduction of duplicated code
####################################################################
* Fix for a CPU hot-add deadlock in microcode update code

* Fix for idle consolidation fallout

* Documentation update for initial kernel direct mapping

-Nicholas A. Bellinger has target fixes for -rc2:

A handful of fixes + minor changes this time around, along with one
important >= v3.9 regression fix for IBLOCK backends. The highlights
include:

– Use FD_MAX_SECTORS in FILEIO for block_device as well as files (agrover)
– Fix processing of out-of-order CmdSNs with iSBD driver (shlomo)
– Close long-standing target_put_sess_cmd() vs. core_tmr_abort_task() race
with the addition of kref_put_spinlock_irqsave() (joern + greg-kh)
– Fix IBLOCK WCE=1 + DPOFUA=1 backend WRITE regression in >= v3.9 (nab + bootc)

Note these four patches are CC’ed to stable.

Also, there is still some work left to be done on the active I/O
shutdown path in target_wait_for_sess_cmds() used by tcm_qla2xxx +
ib_isert fabrics that is still being discussed on the list, and will
hopefully be resolved soon.

kernel news – 14.05.2013

-David Miller and networking:

Several small bug fixes all over:

1) be2net driver uses wrong payload length when submitting MAC list get
requests to the chip. From Sathya Perla.

2) Fix mwifiex memory leak on driver unload, from Amitkumar Karwar.

3) Prevent random memory access in batman-adv, from Marek Lindner.

4) batman-adv doesn’t check for pskb_trim_rcsum() errors, also from Marek
Lindner.

5) Fix fec crashes on rapid link up/down, from Frank Li.

6) Fix inner protocol grovelling in GSO, from Pravin B Shelar.

7) Link event validation fix in qlcnic from Rajesh Borundia.

8) Not all FEC chips can support checksum offload, fix from Shawn Guo.

9) EXPORT_SYMBOL + inline doesn’t make any sense, from Denis Efremov.

10) Fix race in passthru mode during device removal in macvlan, from
Jiri Pirko.

11) Fix RCU hash table lookup socket state race in ipv6, leading to NULL
pointer derefs, from Eric Dumazet.

12) Add several missing HAS_DMA kconfig dependencies, from Geert
Uyttterhoeven.

13) Fix bogus PCI resource management in 3c59x driver, from Sergei
Shtylyov.

14) Fix info leak in ipv6 GRE tunnel driver, from Amerigo Wang.

15) Fix device leak in ipv6 IPSEC policy layer, from Cong Wang.

16) DMA mapping leak fix in qlge from Thadeu Lima de Souza Cascardo.

17) Missing iounmap on probe failure in bna driver, from Wei Yongjun.

-Helge Deller announces parisc updates:

The second round of parisc updates for 3.10 includes build fixes and
enhancements to utilize irq stacks, fixes SMP races when updating PTE
and TLB entries by proper locking and makes the search for the correct
cross compiler more robust on Debian and Gentoo.

-Benjamin Herrenschmidt has powerpc fixes (merge branch):

Here are some more powerpc fixes to apply to 3.10. This is mostly bug
fixes (some of them regressions, some of them I deemed worth merging
now) along with some patches from Li Zhong hooking up the new
context tracking stuff (for the new full NO_HZ)

kernel news – 13.05.2013

-Greg KH announces the release of kernels 3.0.78, 3.4.45, 3.8.13
(“I’m announcing the release of the 3.8.13 kernel.

NOTE, this is the LAST 3.8.y kernel release, please move to the 3.9.y
kernel series at this time. It is end-of-life, dead, gone, buried, and
put way behind us never to be spoken of again. Seriously, move on, it’s
just not worth it anymore.

And for that specific two-letter hardware company that was insisting in
public that I would be maintaining the 3.8.y kernel as a long-term
kernel so that “you will do our maintenance work for us, for free,”
please see figure one.”) and 3.9.2.

-virtio/lguest fixes are announced by Rusty Russell.

-Mark Brown has a small regmap pull request for 3.10:

A couple of small fixes for the debugfs code – make sure we report
hardware errors back up if we encounter them and fix the display of
register maps that make use of striding.

-Dave Airlie has a few DRM fixes :

Hi Linus,

just a few straggling fixes I hoovered up, and an intel fixes pull from
Daniel which fixes some regressions, and some mgag200 fixes from Matrox.

-Linus Torvalds announces 3.10-rc1:

So this is the biggest -rc1 in the last several years (perhaps ever)
at least as far as counting commits go, even if not necessarily in
actual lines (I didn’t check the statistics on that).

Which was unexpected, because while linux-next was fairly big, it
wasn’t exceptionally so. I’m sure Stephen Rothwell will talk about the
statistics of commits that weren’t in -next, we’ll see if that was the
reason..

Anyway, despite the large number of commits, hopefully it’s all
boringly straigthforward. Sure.

Now, even normally, there’s no way to list all the changes, much less
so when it’s an unusually large -rc1. But I can do my “merge shortlog”
again, and it’s worth mentioning (again) that the name attributed to
the merge is *not* necessarily the author of any of the code, it’s
literally just the person who emailed me the pull request. So you can
see this as an approximation of “first-level maintainership” or
something, although even that is somewhat misleading since some of
these things are really done by groups and then there’s one person who
end up sending me the end result.

But it’s somewhat readable, and gives you a reasonable idea of what is
going on. A better idea can be gotten by looking at git directly,
especially since the merge commits often do contain a better
description of what happened. Not that all submaintainers necessarily
always send me that, but most of the merges actually do have
human-readable background information.

It’s possible that I missed something. This really was a busier merge
window than usual. Holler if so,

Linus

kernel news – 10.05.2013

-Firewire fixes by Stefan Richter:

- fix controller removal when controller is in suspended state
– fix video reception on VIA VT6306 with gstreamer, MythTV, and maybe dv4l
– fix a startup issue with Agere/LSI FW643-e2
– error logging improvements and other small updates

-David Woodhouse has “misc minor cleanups” for 3.10:

- Artem’s removal of dead code continues (RPX, MBX860)
– Two krealloc() abuse fixes

This is some miscellaneous cleanups that don’t really belong anywhere
else (or were ignored), that have been sitting in linux-next for some
time. Two of them are fixes resulting from my audit of krealloc() usage
that don’t seem to have elicited any response when I posted them, and
the other three are patches from Artem removing dead code.

-Rafael J. Wysocki has ACPI fixes for -rc1:

These are three urgent ACPICA fixes two of which fix regressions introduced
earlier during this merge window and the third one fixes a potential buffer
overflow that has been there for quite a while (fortunately, it’s not easy
to trigger).

-Chris Mason and btrfs:

These are mostly fixes. The biggest exceptions are Josef’s skinny
extents and Jan Schmidt’s code to rebuild our quota indexes if they get
out of sync (or you enable quotas on an existing filesystem).

The skinny extents are off by default because they are a new variation
on the extent allocation tree format. btrfstune -x enables them, and
the new format makes the extent allocation tree about 30% smaller.

I rebased this a few days ago to rework Dave Sterba’s crc checks on the
super block, but almost all of these go back to rc6, since I though 3.9 was
due any minute.

The biggest missing fix is the tracepoint bug that was hit late in 3.9.
I ran into problems with that in overnight testing and I’m still
tracking it down. I’ll definitely have that fixed for rc2.

-ecryptfs updates as announced by Tyler Hicks:

Improve performance when AES-NI (and most likely other crypto accelerators) is
available by moving to the ablkcipher crypto API. The improvement is more
apparent on faster storage devices. There’s no noticeable change when hardware
crypto is not available.

kernel news – 06.04.2013

-Gleb Natapov announces KVM updates for 3.10 merge window:

Highlights of the updates are:

general:
– new emulated device API
– legacy device assignment is now optional
– irqfd interface is more generic and can be shared between arches
x86:
– VMCS shadow support and other nested VMX improvements
– APIC virtualization and Posted Interrupt hardware support
– Optimize mmio spte zapping
ppc:
– BookE: in-kernel MPIC emulation with irqfd support
– Book3S: in-kernel XICS emulation (incomplete)
– Book3S: HV: migration fixes
– BookE: more debug support preparation
– BookE: e6500 support
ARM:
– reworking of Hyp idmaps
s390:
– ioeventfd for virtio-ccw

And many other bug fixes, cleanups and improvements.

-There is a MFD pull request from Samuel Ortiz targetting also 3.10:

Hi Linus,

This is the MFD pull request for the 3.10 merge window. There is one merge
conflict with your tree, and I fixed it for reference in my mfd-3.10-merge
branch.

For 3.10 we have a few new MFD drivers for:

- The ChromeOS embedded controller which provides keyboard, battery and power
management services. This controller is accessible through i2c or SPI.

- Silicon Laboratories 476x controller, providing access to their FM chipset
and their audio codec.

- Realtek’s RTS5249, a memory stick, MMC and SD/SDIO PCI based reader.

- Nokia’s Tahvo power button and watchdog device. This device is very similar
to Retu and is thus supported by the same code base.

- STMicroelectronics STMPE1801, a keyboard and GPIO controller supported by
the stmpe driver.

- ST-Ericsson AB8540 and AB8505 power management and voltage converter
controllers through the existing ab8500 code.

Some other drivers got cleaned up or improved. In particular:

- The Linaro/STE guys got the ab8500 driver in sync with their internal code
through a series of optimizations, fixes and improvements.

- The AS3711 and OMAP USB drivers now have DT support.

- The arizona clock and interrupt handling code got improved.

- The wm5102 register patch and boot mechanism also got improved.

-Joerg Roedel has IOMMU updates:

The updates are mostly about the x86 IOMMUs this time. Exceptions are
the groundwork for the PAMU IOMMU from Freescale (for a PPC platform)
and an extension to the IOMMU group interface. On the x86 side this
includes a workaround for VT-d to disable interrupt remapping on broken
chipsets. On the AMD-Vi side the most important new feature is a kernel
command-line interface to override broken information in IVRS ACPI
tables and get interrupt remapping working this way. Besides that there
are small fixes all over the place.

-Ingo Molnar has timers-nohz updates:

his tree from Frederic Weisbecker adds a new, (exciting! core kernel
feature to the timer and scheduler subsystems: ‘full dynticks’, or
CONFIG_NO_HZ_FULL=y.

This feature extends the nohz variable-size timer tick feature from idle
to busy CPUs (running at most one task) as well, potentially reducing the
number of timer interrupts significantly.

This feature got motivated by real-time folks and the -rt tree, but the
general utility and motivation of full-dynticks runs wider than that:

– HPC workloads get faster: CPUs running a single task should be able to
utilize a maximum amount of CPU power. A periodic timer tick at HZ=1000
can cause a constant overhead of up to 1.0%. This feature removes that
overhead – and speeds up the system by 0.5%-1.0% on typical distro
configs even on modern systems.

– Real-time workload latency reduction: CPUs running critical tasks
should experience as little jitter as possible. The last remaining
source of kernel-related jitter was the periodic timer tick.

– A single task executing on a CPU is a pretty common situation,
especially with an increasing number of cores/CPUs, so this feature
helps desktop and mobile workloads as well.

The cost of the feature is mainly related to increased timer-reprogramming
overhead when a CPU switches its tick period, and thus slightly longer
to-idle and from-idle latency.

Configuration-wise a third mode of operation is added to the existing two
NOHZ kconfig modes:

– CONFIG_HZ_PERIODIC: [formerly !CONFIG_NO_HZ], now explicitly named as a
config option. This is the traditional Linux periodic tick design:
there’s a HZ tick going on all the time, regardless of whether a CPU is
idle or not.

– CONFIG_NO_HZ_IDLE: [formerly CONFIG_NO_HZ=y], this turns off the
periodic tick when a CPU enters idle mode.

– CONFIG_NO_HZ_FULL: this new mode, in addition to turning off the tick
when a CPU is idle, also slows the tick down to 1 Hz (one timer
interrupt per second) when only a single task is running on a CPU.

The .config behavior is compatible: existing !CONFIG_NO_HZ and
CONFIG_NO_HZ=y settings get translated to the new values, without the user
having to configure anything. CONFIG_NO_HZ_FULL is turned off by default.

This feature is based on a lot of infrastructure work that has been
steadily going upstream in the last 2-3 cycles: related RCU support and
non-periodic cputime support in particular is upstream already.

This tree adds the final pieces and activates the feature. The pull
request is marked RFC because:

– it’s marked 64-bit only at the moment – the 32-bit support patch is
small but did not get ready in time.

– it has a number of fresh commits that came in after the merge window.
The overwhelming majority of commits are from before the merge window,
but still some aspects of the tree are fresh and so I marked it RFC.

– it’s a pretty wide-reaching feature with lots of effects – and while
the components have been in testing for some time, the full combination
is still not very widely used. That it’s default-off should reduce its
regression abilities and obviously there are no known regressions with
CONFIG_NO_HZ_FULL=y enabled either.

– the feature is not completely idempotent: there is no 100% equivalent
replacement for a periodic scheduler/timer tick. In particular there’s
ongoing work to map out and reduce its effects on scheduler
load-balancing and statistics. This should not impact correctness
though, there are no known regressions related to this feature at this
point.

– it’s a pretty ambitious feature that with time will likely be enabled
by most Linux distros, and we’d like you to make input on its
design/implementation, if you dislike some aspect we missed. Without
flaming us to crisp!

Future plans:

– there’s ongoing work to reduce 1Hz to 0Hz, to essentially shut
off the periodic tick altogether when there’s a single busy task on a
CPU. We’d first like 1 Hz to be exposed more widely before we go for
the 0 Hz target though.

– once we reach 0 Hz we can and remove the periodic tick assumption from
nr_running>=2 as well, by essentially interrupting busy tasks only as
frequently as the sched_latency constraints require us to do – once
every 4-40 msecs, depending on nr_running.

I am personally leaning towards biting the bullet and doing this in v3.10,
like the -rt tree this effort has been going on for too long – but the
final word is up to you as usual.

More technical details can be found in Documentation/timers/NO_HZ.txt.

-pwm updates for -rc1 from Thierry Reding:

Nothing very exciting this time around. A couple of bug fixes and a lot
of cleanup across the board. The DaVinci 8xx family of SoCs now use the
same driver as the AM33xx family.

Many thanks to Axel Lin and Jingoo Han who have done a great job fixing
various bugs and inconsistencies.

kernel news – 01.05.2013

-Mauro Carvalho Chehab has media updates for 3.10-rc1:

- OF documentation and patches at core and drivers, to be used by
for embedded media systems;
- some I2C drivers used on go7007 were rewritten/promoted from staging:
sony-btf-mpx, tw2804, tw9903, tw9906, wis-ov7640, wis-uda1342;
- add fimc-is driver (Exynos);
- add a new radio driver: radio-si476x;
- add a two new tuners r820t and tuner_it913x;
- split camera code on em28xx driver and add more models;
- the cypress firmware load is used outside dvb usb drivers. So,
move it to a common directory to make easier to re-use it;
- siano media driver updated to work with sms2270 devices;
- several work done in order to promote go7007 and solo6x1x out of
staging (still, there are some pending issues);
- several API compliance fixes at v4l2 drivers that don’t behave as
expected;
- as usual, lots of driver fixes, improvements, cleanups and new
device addition at the existing drivers.

-Also, Mauro announces edac fixes:

- i7300_edac currently reports a wrong number of DIMMs when
the memory controller is in single channel mode;

- on some Sandy Bridge machines, the EDAC driver bails out
as one of the PCI IDs used by the driver is hidden by BIOS.
As the driver uses it only to detect the type of memory,
make it optional at the driver.

-Rafael J. Wysocki has ACPI and PM updates:

The cpufreq changes are the largest batch this time, mostly due to
the Viresh Kumar’s work on the core cleanup. The feature most likely
to make some headlines is the ARM big.LITTLE cpufreq driver, also from
Viresh.

Next in size is the cpuidle update with the majority of work done by
Daniel Lazcano. That is code consolidation and some cleanups mostly,
hopefully non-exciting stuff.

In addition to the above we have a usual ACPICA update containing
material from February and March releases, an update of the ACPI core
related to hotplug and a number of assorted fixes and cleanups in
ACPI and PM core.

Highlights:

- ARM big.LITTLE cpufreq driver from Viresh Kumar.

- exynos5440 cpufreq driver from Amit Daniel Kachhap.

- cpufreq core cleanup and code consolidation (several ARM drivers go
to drivers/cpufreq among other things) from Viresh Kumar and
Stratos Karafotis.

- cpufreq scalability improvement from Nathan Zimmer.

- AMD “frequency sensitivity feedback” powersave bias for the ondemand
cpufreq governor from Jacob Shin.

- cpuidle code consolidation and cleanups from Daniel Lezcano.

- ARM OMAP cpuidle fixes from Santosh Shilimkar and Daniel Lezcano.

- ACPICA fixes and other improvements from Bob Moore, Jung-uk Kim,
Lv Zheng, Yinghai Lu, Tang Chen, Colin Ian King, and Linn Crosetto.

- ACPI core updates related to hotplug from Toshi Kani, Paul Bolle,
Yasuaki Ishimatsu, and yours truly.

- Intel Lynxpoint LPSS (Low-Power Subsystem) support improvements
from myself and Andy Shevchenko.

-There are arch/metag changes as announced by James Hogan:

- Various fixes for the interrupting perf counter handling in metag’s
perf backend.
– Add OProfile support based on perf.
– Sets up cache partitions for SMP so bootloader doesn’t have to.
– Patch from Paul Bolle to remove ARCH_POPULATES_NODE_MAP again
(touches microblaze too).
– Add TLS pointer regset to metag ptrace api.
– Add exported metag DSP extended context handling header .
– Increase defconfig log buffer size to 128KiB.
– Various fixes, typos, missing exports.

-Trond Myklebust has NFS client changes:

NFS client bugfixes and cleanups for 3.10

- NLM: stable fix for NFSv2/v3 blocking locks
- NFSv4.x: stable fixes for the delegation recall error handling code
- NFSv4.x: Security flavour negotiation fixes and cleanups by Chuck Lever
- SUNRPC: A number of RPCSEC_GSS fixes and cleanups also from Chuck
- NFSv4.x assorted state management and reboot recovery bugfixes
- NFSv4.1: In cases where we have already looked up a file, and hold a
valid filehandle, use the new open-by-filehandle operation instead of
opening by name.
- Allow the NFSv4.1 callback thread to freeze
- NFSv4.x: ensure that file unlock waits for readahead to complete
- NFSv4.1: ensure that the RPC layer doesn’t override the NFS session
table size negotiation by limiting the number of slots.
- NFSv4.x: Fix SETATTR spec compatibility issues

-Matt Fleming has various EFI fixes:

This first pull request is a merge of v3.9 into f53f292, as requested by
Ingo because I botched the original merge of v3.9-rc8 (which is currently
in tip/x86/efi) by losing the “select UCS2_STRING” line from
drivers/firmware/Kconfig. An equivalent line has been added to arch/ia64
in this merge.

-Catalin Marinas has an arm64 pull request for -rc1:

Main features:
- Versatile Express SoC (model) support – DT files and Kconfig entries
(there are no arch/arm64/mach-* directories). The bulk of the code has
already been moved to drivers/ as part of the ARM SoC clean-up.
- Basic multi-cluster support (CPU logical map initialised from the DT).
- Simple earlyprintk support for UART 8250/16550 and FastModel console
output.
- Optimised kernel library bitops and string functions.
- Automatic initialisation of the irqchip and clocks via DT.

-David Teigland and dlm updates for 3.10:

When the kernel clears flocks/plocks during close, it calls posix
unlock when there are flocks but no posix locks. Without this
patch, that unnecessary posix unlock is passed to userland
(dlm_controld), across the cluster, and back to the kernel.
This can create a lot of plock activity, even when no posix
locks had been used.

This patch copies the nfs approach, and skips the full posix
unlock if there is no plock found during the vfs unlock phase.

-James Bottomley has SCSI updates for the current merge window:

This is the first round, consisting mostly of drivers and patches
submitted 3 weeks ago. Since I’ve been travelling quite a bit, there
will be a second round just before the merge window closes for all the
patches three weeks or newer, or which got flagged for my attention
after 10 April.

The patch set is mostly driver updates (qla4, qla2 [ISF support
updates], lpfc, aacraid [dual firmware image support]) and a few bug
fixes.

-libata updates are present thanks to Jeff Garzik:

Summary:

1) More ACPI fixes, cleanups

2) Minor cleanups for sata_highbank, pata_at32, pata_octeon_cf,
sata_rcar

3) pata_legacy: small bug found in opti chipset code (untested fix,
due to ancient h/w)

4) sata_fsl: RX water mark config knob, some h/w needs it

5) pata_imx: cleanups, DeviceTree support

6) SCSIATA translator: properly export translator version,
not device firmware version

-Al Viro updates signal, take one:

Mostly about syscall wrappers this time; there will be another pile with
patches in the same general area from various people, but I’d rather push
those after both that and vfs.git pile are in. Please, pull from

git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal for-linus

Shortlog:
Al Viro (20):
get rid of duplicate logics in __SC_….[1-6] definitions
teach SYSCALL_DEFINE how to deal with long long/unsigned long long
consolidate cond_syscall and SYSCALL_ALIAS declarations
make HAVE_SYSCALL_WRAPPERS unconditional
make SYSCALL_DEFINE-generated wrappers do asmlinkage_protect
switch signalfd{,4}() to COMPAT_SYSCALL_DEFINE
convert sendfile{,64} to COMPAT_SYSCALL_DEFINE
switch epoll_pwait to COMPAT_SYSCALL_DEFINE
switch getrusage() to COMPAT_SYSCALL_DEFINE
convert vmsplice to COMPAT_SYSCALL_DEFINE
consolidate compat lookup_dcookie()
merge compat sys_ipc instances
get rid of compat_sys_semctl() and friends in case of ARCH_WANT_OLD_COMPAT_IPC
x86: sys32_kill and sys32_mprotect are pointless
x86: trim sys_ia32.h
ppc compat wrappers for add_key(2) and request_key(2) are pointless
sparc: no need to sign-extend in sync_file_range() wrapper
make do_mremap() static
get rid of union semop in sys_semctl(2) arguments
syscalls.h: slightly reduce the jungles of macros

-Theodore Ts’o updates ext4:

Mostly performance and bug fixes, plus some cleanups. The one new
feature this merge window is a new ioctl EXT4_IOC_SWAP_BOOT which
allows installation of a hidden inode designed for boot loaders.