linux-kernel - root MD array is still in use upon shutdown possible fix

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 6 Oct 2006 20:26:42 +0200 (CEST)
From:	Czigola Gabor <czigola@...e.hu>
To:	linux-kernel@...r.kernel.org
Subject: root MD array is still in use upon shutdown possible fix

Hi!

When my root filesystem is on an MD (RAID5) array, I can't cleanly shut 
down (trying to change the array ro, even when nothing else than the 
kernel threads and init and one bash are running, and the root fs is ro 
remounted), because I've got "md: md0 still in use" kernel messages. 
Usually it doesn't cause any problems, but it possibly could leave the 
array in an inconsistent state (resync required after reboot).

I made a patch for md.c, based on the thread on "Can't get md array to 
shut down cleanly" started at 2006-07-06 on linux-raid@...r.

The problem is reproducible on kernel v. 2.6.17.5 and 2.6.17.11, this 
patch is made for the latter.

Please check this patch, for me it does work, but I'm not sure, that it 
doesn't break something else. I'm not on the list, please CC me.

Here is the diff for drivers/md/md.c:

2789c2789
< 		if (atomic_read(&mddev->active)>2) {
---
> 		if (atomic_read(&mddev->active)>2 && !ro) {

-- 
Czigola, Gabor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/