diff --git a/mdadm.rules b/mdadm.rules
index 8ff3847..5fffb8b 100644
--- a/mdadm.rules
+++ b/mdadm.rules
@@ -9,6 +9,7 @@ SUBSYSTEM=="block", ACTION=="remove", ENV{ID_FS_TYPE}=="linux_raid_member", \
 	RUN+="/sbin/mdadm -If $env{DEVNAME}"
 
 ENV{rd_NO_MDIMSM}=="?*", GOTO="md_imsm_inc_end"
+ENV{noiswmd}=="?*", GOTO="md_imsm_inc_end"
 # In case the initramfs only started some of the arrays in our container,
 # run incremental assembly on the container itself.  Note: we ran mdadm
 # on the container in 64-md-raid.rules, and that's how the MD_LEVEL
diff --git a/mdadm.spec b/mdadm.spec
index fe6f8b1..31cd89e 100644
--- a/mdadm.spec
+++ b/mdadm.spec
@@ -74,6 +74,9 @@ fi
 %attr(0700,root,root) %dir /var/run/mdadm
 
 %changelog
+* Wed Aug 04 2010 Doug Ledford <dledford@redhat.com> - 3.1.3-0.git20100804.2
+- Add udev patch to not have incremental assembly in two rules files
+
 * Wed Aug 04 2010 Doug Ledford <dledford@redhat.com> - 3.1.3-0.git20100804.1
 - Update to latest upstream release (resolves an issue with stale lock
   files on the md device map file)