|
|
Subscribe / Log in / New account

The conclusion of the 3.5 merge window

By Jonathan Corbet
June 5, 2012
Linus closed the 3.5 merge window on June 2; the announcement for the 3.5 prepatch came one day later. Just under 1,000 patches were pulled into the mainline after the writing of last week's merge window summary, for a total of 9,534 for the merge window as a whole. Some of the more significant changes pulled at the end of the merge window include:

  • The HFS filesystem has gained native language support (NLS) capabilities, with codepages added for several languages.

  • A process's directory under /proc now includes a children file containing the IDs of its child processes.

  • The kcmp() system call has been added. Its purpose is to help user space checkpoint/restore utilities to determine whether two processes share a given resource or not; see this article for a description of the interface.

  • Also for checkpoint/restore: the prctl() system call has gained options to set the beginning and end of the argv and environment areas and the executable file a process is running.

  • The ext4 filesystem now has support for metadata checksumming, a feature which should help to catch metadata corruption that might otherwise escape notice. This feature requires an on-disk format change (to store the checksum), so it must be turned on explicitly. Once this feature is enabled, the filesystem can only be mounted read-only on older kernels. See this article for more information on the metadata checksum feature.

  • A lot of changes have gone in to improve the handling of system-specific features on Sony laptops.

  • The new skew_tick= boot option controls whether the system skews timer ticks on a per-CPU basis to minimize contention on the xtime_lock lock. It defaults to off; turning it on can reduce jitter on some workloads, but will also increase power consumption.

  • The "frontswap" mechanism, part of the transcendent memory family of technologies, sneaked its way into the mainline just after the -rc1 release.

  • The FUSE filesystem API has added an operation to implement the fallocate() system call.

  • Two new drivers were added at the end of the merge window; they enable AUO K1900 and K1901 epaper display controllers and Emma Mobile STI timers.

Changes visible to kernel developers include:

  • The task_work_add() function, useful for requesting that a function be run in the context of a specific process, has been added. See this article for a description of the task_work_add() API.

  • The SUNRPC code has a new utility function:

        int svc_bind(struct svc_serv *serv, struct net *net);
    
    Its purpose is to handle service registration in the given network context; svc_bind() is exported GPL-only.

  • struct inode_operations has a new update_time() function whose job is to provide any needed special handling for changes to any of the file timestamps. The file_update_time() prototype has been changed: it now returns an int that can indicate that the operation failed. Failures to update the last-access time are now explicitly ignored; this is done to ensure that atime update failures don't make the filesystem unreadable. This work has been generalized out of the btrfs filesystem; see this article for a description of how atime updates can go wrong otherwise.

At this point, the addition of features for the 3.5 development cycle should be at an end unless something sneaks in before -rc2. If the usual pattern holds, the final 3.5 release can be expected right around the beginning of August.

Index entries for this article
KernelReleases/3.5


to post comments


Copyright © 2012, Eklektix, Inc.
This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds