Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753430AbcCCBIE (ORCPT ); Wed, 2 Mar 2016 20:08:04 -0500 Received: from mail-lb0-f173.google.com ([209.85.217.173]:35491 "EHLO mail-lb0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750797AbcCCBID (ORCPT ); Wed, 2 Mar 2016 20:08:03 -0500 MIME-Version: 1.0 Date: Wed, 2 Mar 2016 17:08:00 -0800 Message-ID: Subject: allocate an official device major number for virtio device? From: Jin Qian To: linux-kernel@vger.kernel.org Cc: jsharkey@google.com, digit@google.com, Greg Kroah-Hartman , pprabhu@google.com, Yu Ning Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 581 Lines: 17 Hi - Can we allocate an official device major number for virtio devices? Currently it's using 240-254 (LOCAL/EXPERIMENTAL USE). The reason we ask for this is because userspace will need to treat virtio block devices differently and need a way to detect such device. For example, it checks major number to detect scsi and mmc device. https://android-review.googlesource.com/#/c/195240 With dynamic major numbers 240-254, we might treat other devices as virtio block device incorrectly. Also open for suggestions on what's the correct way to handle this. Thanks in advance! jin