linux-kernel - Question: DLPAR remove with mounted partitions.

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130623172632.GA5685@oc6784271780.ibm.com>
Date:	Sun, 23 Jun 2013 12:26:32 -0500
From:	"Philip J. Kelleher" <pjk1939@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org
Subject: Question: DLPAR remove with mounted partitions.

Hello all,

I have a question regarding a DLPAR remove operations with a mounted
partition.

I am writing a block level device driver that will support DLPAR remove
operations and I was doing some testing with a partition from the adapter
still mounted while I ran a DLPAR remove.

The remove completed successfully and lspci doesn't list my device
anymore. However, I ran the 'df' command and noticed that the partition
was still listed in the output. I, then, ran an 'ls' on the mount point
for that partition and a Kernel Panic occured.

I fixed the panic by setting the queuedata member to NULL in the
request_queue object and checking the request_queue for a NULL queuedata
in the make_request function.

My main question is this: Should the Kernel allow for a successful DLPAR
remove while there are still reference counts still active on the
device? If so, is my implementation the correct way to countering the issue?

Thanks in advance.

Regards,
-Philip Kelleher

--
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/