> Indeed, good catch. Do we need the same treatment for> __set_page_dirty_buffers() that can be called by way of> clear_page_dirty_for_io()?Indeed. I posted a patch fixed __set_page_dirty() too. plz seeSubject: [PATCH] __set_page_dirty uses spin_lock_irqsave instead ofspin_lock_irq