linux-kernel - Re: linux-next: Tree for April 1 (virtio

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BBB7A44.2020300@redhat.com>
Date:	Tue, 06 Apr 2010 14:15:32 -0400
From:	john cooper <john.cooper@...hat.com>
To:	Rusty Russell <rusty@...tcorp.com.au>
CC:	Randy Dunlap <randy.dunlap@...cle.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Marc Haber <mh+qemu-devel@...schlus.de>, john.cooper@...hat.com
Subject: Re: linux-next: Tree for April 1 (virtio_blk warning)

Rusty Russell wrote:
> On Fri, 2 Apr 2010 02:43:12 am Randy Dunlap wrote:
>> On Thu, 1 Apr 2010 17:23:17 +1100 Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>> Changes since 20100331:
>>
>> drivers/block/virtio_blk.c:228:13: warning: multi-character character constant
>>
>> due to:
>>
>> 	if (cmd == 'VBID') {
> 
> John?  That looks suspiciously like untested code.

It does work as advertised although gcc is obliged to squawk
at multi-byte character constants due to portability concerns.

Note I'd intended that only as an example for the benefit of
completeness in the associated patch set, and to stick out
like a sore thumb of sorts.  Marc Haber had suggested exposing
the id string to the guest userland via /sys which is what I
had expected to displace the loose ioctl example above.  In
fact that discussion is what prodded revisiting this issue in
the first place.

Unsure whether Marc (cc'ed here) is still planning to pursue
that interface so unless I hear something to the contrary in
the next day or so I'll package up a suitable ioctl interface
and forward a patch.  It doesn't hurt to provide ioctl access
to the info in addition to exposing it via /sys, but I'd
hoped the latter would overshadow the need to do so.

-john

-- 
john.cooper@...hat.com
--
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/