lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 23 Jun 2011 10:45:07 +1000
From:	Stephen Rothwell <>
Subject: Re: mmotm 2011-06-22-13-05 uploaded

Hi Andrew,

On Wed, 22 Jun 2011 13:05:19 -0700 wrote:
> The mm-of-the-moment snapshot 2011-06-22-13-05 has been uploaded to
> It contains the following patches against 3.0-rc4:
> memcg-fix-node_start-end_pfn-definition-for-mm-page_cgroupc.patch
> mm-move-vmtruncate_range-to-truncatec.patch
> mm-move-shmem-prototypes-to-shmem_fsh.patch
> tmpfs-take-control-of-its-truncate_range.patch
> tmpfs-add-shmem_read_mapping_page_gfp.patch
> drivers-rtc-rtc-ds1307c-add-support-for-rtc-device-pt7c4338.patch
> um-add-asm-percpuh.patch
> romfs-fix-romfs_get_unmapped_area-param-check.patch
> include-linux-compath-declare-compat_sys_sendmmsg.patch
> drivers-misc-lkdtmc-fix-race-when-crashpoint-is-hit-multiple-times-before-checking-count.patch
> mm-memory-failurec-fix-spinlock-vs-mutex-order.patch
> mm-fix-assertion-mapping-nrpages-==-0-in-end_writeback.patch
> taskstats-dont-allow-duplicate-entries-in-listener-mode.patch
> drm-ttm-use-shmem_read_mapping_page.patch
> drm-i915-use-shmem_read_mapping_page.patch
> drm-i915-use-shmem_truncate_range.patch
> drm-i915-more-struct_mutex-locking.patch
> drm-i915-more-struct_mutex-locking-fix.patch
> mm-cleanup-descriptions-of-filler-arg.patch
> mm-truncate-functions-are-in-truncatec.patch
> mm-tidy-vmtruncate_range-and-related-functions.patch
> mm-consistent-truncate-and-invalidate-loops.patch
> mm-pincer-in-truncate_inode_pages_range.patch
> tmpfs-no-need-to-use-i_lock.patch
> mm-nommuc-fix-remap_pfn_range.patch

As an experiment, I have applied all the above patches (everything
between origin.patch and linux-next.patch exclusive) to my "fixes" tree
so that they will be in linux-next immediately after Linus' tree and
before anything else.   I am assuming that these patches are going to be
sent to Linus shortly (if you haven't already).   I will point the
akpm-start branch of linux-next to be just after the above patches (so
akpm-start..akpm-end will contain everything else in linux-next).

If this is a problem, let me know and I will drop them again.  Otherwise,
they will disappear from my tree when Linus' takes tham from you.
Stephen Rothwell          

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists