From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrian Bunk Subject: RFC: dm patches for 2.6.16 Date: Fri, 24 Nov 2006 04:24:44 +0100 Message-ID: <20061124032444.GH28363@stusta.de> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="WIyZ46R2i8wDzkSu" Return-path: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: dm-devel@redhat.com Cc: Mark McLoughlin , Michal Miroslaw , Daniel Kobras , Alasdair G Kergon List-Id: dm-devel.ids --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The following attached patches seem to make sense for 2.6.16: Added in 2.6.17.11 and 2.6.18: dm: BUG/OOPS fix Added in 2.6.17.12 and 2.6.18: dm snapshot: unify chunk_size dm: add module ref counting dm: mirror sector offset fix dm: Fix deadlock under high i/o load in raid1 setup. Added in 2.6.19: dm snapshot: fix metadata writing when suspending For an easier review, I've attached the patches. Do these patches look OK for 2.6.16, or should I not apply some or all? Are there any critical patches I missed? TIA Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dm-bug-oops-fix.patch" --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --WIyZ46R2i8wDzkSu--