Skip to main content

rhel6-testing-042stab056.8

Since 042stab056.5:
  • [cfq] kernel BUG at block/cfq-iosched.c:386 has been fixed (PCLIN-30890)
  • [fuse] added possibility to disable fuse O_DIRECT with help of fs.fuse_ext_caps sysctl (enabled by default) (debug for PSBM-13075)
  • [fuse] flush writeback data on file close. In particular this fixes checkpointing (PSBM-13226)
  • [fuse] several other bugfixes
  • [quota] remounting of FS with quota on ploop could crash host (PSBM-13231)
  • [fs/writeback] writeback writer throttler algorithm has been enhanced
  • [mount namespaces] mount namespaces support for has been added. This is required for Fedora 17 (PSBM-13004). Note: online migration support has not been added yet
  • [cpt] kernel BUG at kernel/cpt/rst_socket.c:407 (on a self-connected socket restore) fixed (PSBM-13367)
  • [cpt] sleep-in-atomic at dumping cgroup has been fixes (PSBM-13297)
  • [cpt] timerfs irq-safe locking has been fixed
  • [cpt] false positive error messages "_rst_get_object: wrong object type" has been fixed (PSBM-13303)
  • [fuse] "fs.fuse_ext_caps" sysctl has been removed. Now we need to provide fuse mount options to enable features:
    • "writeback_enable" mount option to enable writeback for fuse mount
    • "direct_enable" mount option to enable direct IO for fuse mount
  • [fuse] show writeback and dio options in proc
  • [fuse] file release should make sure writeback is finished
  • [iov_iter] direct_IO_page interface has been added. Required for efficient fuse io_kaio (PSBM-12830)
  • [oom] oom reports now the current fuse writeback pages counter
  • [time] CT uptime is calculated incorrectly in cases like host suspend (PCLIN-30011)
  • [fairsched] accuracy of idle/iowait time stats reported through /proc/stat has been increased (PCLIN-30724)
  • [fairsched] context switch latency on an almost idle node has been significantly decreased (PSBM-11477)
  • [ploop] support for 'expanded' format to io_kaio, support for snapshot, merge and pcopy (migrate) operations has been added (PSBM-12830)
  • [ploop] we support only ploop over NFS v3 => ploop mount over NFSv4 has been prohibited (PSBM-13376)
  • [ploop] ploop balloon discard could ignore errors and hang (PSBM-13290)
  • [ovs/ipv6] kernel ABI has been restored, hypervisor modules should compile fine now (PSBM-13383)
  • [ploop] disable ENOSPC checks for preallocated and raw images
  • [blkcg] allocate per-cpu statistics from worker thread
  • [ipv6] change neighbour table hash for ipv6
Labels:

Comments

Post a Comment

Popular posts from this blog

Feedly launches 'Feedly Cloud' sync platform, new web interface

Feedly, one of the leading Google Reader replacement services, announced major restructuring of its services today with a new cloud infrastructure and web interface. Posted on its official blog, Feedly unveiled what it calls "Feedly Cloud", a scalable infrastructure it says is ready to replace Google Reader. The new Feedly Cloud provides several benefits, the first of which is one-click import from Google Reader -- new users to the service can now simply pull everything over seamlessly from their Google account and start using Feedly right away. Existing users will simply have to make sure that they have the latest version of Feedly installed, and their accounts will be migrated to Feedly Cloud over the next few days. Additionally, the new service allowed Feedly to create a stand-alone web interface (found simply at cloud.feedly.com) that works in all major browsers without plugins or extensions. The transition to Feedly Cloud has another benefit, and that is the abilit...
Post a Comment
Read more

Google+ Rolls Out Restricted Communities for Corporate Users

Google this week rolled out a new Google+ security feature for organizations intended to help them keep certain conversations private from the larger Web. Much like Microsoft's Yammer, Google+ restricted communities will only allow access to approved employees. "Whether it's designs of your beta product or notes from your team off-site, anything you post will remain restricted to the organization," Google+ product manager Michael Cai wrote in a blog post. Community administrators can decide whether the site will remain open to everyone at the company, or kept private by invitation only. Google+ also allows for people outside of your domain — clients, agencies, business partners — to join the conversation.
Post a Comment
Read more