On Tue, Feb 12, 2019 at 11:18:22PM +0800, cgxu519 wrote:
On 2/12/19 5:02 PM, Greg KH wrote:Why do you need to know the minor range? What can userspace do with
On Tue, Feb 12, 2019 at 04:47:39PM +0800, Chengguang Xu wrote:I'll remove this part in V2. Do you have any idea how to get the minor
Currently chardev allows to share major, showingYou are changing the format of a userspace file, what tools are going to
major with minor range for chardev will be more
helpful.
Signed-off-by: Chengguang Xu <cgxu519@xxxxxxx>
---
fs/char_dev.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/char_dev.c b/fs/char_dev.c
index b25b1da097d5..6f00acdeb308 100644
--- a/fs/char_dev.c
+++ b/fs/char_dev.c
@@ -55,7 +55,9 @@ void chrdev_show(struct seq_file *f, off_t offset)
mutex_lock(&chrdevs_lock);
for (cd = chrdevs[major_to_index(offset)]; cd; cd = cd->next) {
if (cd->major == offset)
- seq_printf(f, "%3d %s\n", cd->major, cd->name);
+ seq_printf(f, "%3d %s (%u-%u)\n", cd->major, cd->name,
+ cd->baseminor,
+ cd->baseminor + cd->minorct - 1);
break when you do this?
range info for particular major? Or adding a similar file to somewhere
under /sys is acceptable?
this that actually matters?