Home > episodes > 2009/07/08 Linux Kernel Podcast

2009/07/08 Linux Kernel Podcast

Audio: http://media.libsyn.com/media/jcm/linux_kernel_podcast_20090708.mp3

I’ve been in the air for 32 hours over the past few days, on a 3 day trip to Japan, apologies for lag, jetlag, and catchup I’m now playing.

For Wednesday, July 8th 2009, I’m Jon Masters with a summary of today’s LKML traffic.

In today’s issue: Modules, OOM, Lockless Ring Buffer, and VFAT.

Modules. In the second module-related item of the week, Siarhei Liakh posted a patch adding support for RODATA protection (via the RO/NX page protection bits) to kernel modules. This affords LKMs (Loadable/Linux Kernel Modules) the same protections as regular kernel code, using available hardware protection mechanisms for enforcement. Arjan van de Ven expressed his approval.

OOM. Another recent OOM cause was isolated in vmscan for systems without swap (or otherwise with more anon pages than file pages). Wu Fengguang says that he has tested the latest “vmscan don’t isolate too many pages” patch and that it solves his OOM, but now the process entering reclaim could sleep long enough to trigger a soft-lockup watchdog instead.

Lockless Ring Buffer. Steven Rostedt posted to let us know about his lockless ringbuffer, which has been discussed before and which is covered in an excellent story this week on Linux Weekly News. Do be sure to take a look at the page swap mechanism for which a patent application has been filed – and be sure to read Steven’s excellent paper/description on the process.

VFAT. Andrew Tridgell posted a summary of the VFAT discussions, and noted a new tree on kernel.org containing his previous proposed ‘workaround’. He isn’t confident that the current patches will make it into the kernel – for many reasons – but is willing to maintain the tree and hopes that he can address some of the technical concerns that have been raised before pushing for inclusion in the kernel once again.

In today’s miscellaneous items: a fix to elfcore.h to enable building UML (Parag Warudkar), some wireless tree updates (John Linville), a patch adding support for the security processor chip and a separate patch adding a driver for the “Restricted Access Region Register” (apparently an ability to restrict access to memory ranges from the CPU) on the Intel MID Platform (Mark Allyn), various cleanups to MAINTAINERS (Joe Perches), some minor powerpc cleanups (Ben Herrenschmidt), some input updates (Dmitry Torokhov), a conversion of ext2 to use the new truncate mechanism (Nick Piggin), a new uevent emmission on block device write protect attribution change, some Power Management updates (Rafael J. Wysocki), and some System 390 updates (Martin Schwidefsky).

Finally today, your author continues to be interested in the memory c-group notification patches, which should make it possible to implement proper memory reservations in the GNU C-library, if it is wired up that way around. I would love to know whether application developers are looking at this – imagine Firefox selectively relinquishing cached web pages from memory on demand.

In today’s announcements: SCST Target driver support for Emulex lpfc FC/FCoE adapters. Vladislav Bolkhovitin posted to announce support for lpfc adapters to be placed in ISCSI initiator and/or target mode using the lpfc SCST driver kit, available on scst.sourceforge.net.

The latest kernel release is 2.6.31-rc2, which was released by Linus over the 4th July weekend.

Stephen Rothwell posted a linux-next tree for July 8th. Since Tuesday, the “sfi” tree was undropped, the tree still fails to build in an allyesconfig build configuration on powerpc, and a number of other conflicts emerged. The total sub-tree count remains steady at 131 sub-trees in the compose.

That’s a summary of today’s Linux Kernel Mailing List traffic, for further information visit www.kernel.org. I’m Jon Masters.

  • Print this article!
  • del.icio.us
  • Facebook
  • TwitThis
  • Identi.ca
  • Digg
  • Google Bookmarks
  • Slashdot
  • RSS
Categories: episodes Tags:
  1. No comments yet.
  1. No trackbacks yet.