All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluce.liguifu@huawei.com (liguifu (C))
Subject: 答复: [PATCH 08/11] erofs: support special inode
Date: Wed, 1 Aug 2018 08:40:05 +0000	[thread overview]
Message-ID: <9156E5F840CEC74FB517F66C6FB59A33015789DA@dggemi525-mbx.china.huawei.com> (raw)
In-Reply-To: <c78b4103-e536-396e-dfa9-da307fd78058@huawei.com>

Hi 
# Test special device of erofs
we have test four special device, like char device, block device, pipe device and sock decive
using new_encode_dev to create device number in the image created by mkfs.erofs
specail devices node were created in the  Ubuntu 16.04 LTS 4.4.0-104-generic, 
the source codes is based on LDD3 source which coming from https://github.com/duxing2007/ldd3-examples-3.x/tree/origin/linux-4.4.y

Test char devices, block device, pipe device file
step 1, build ldd3 codes 
step 2, install scull.ko sbull.ko and make device node with mknod cmd 

$ cat  /proc/devices|grep scull
246 scull
246 scullp
246 sculla

$ cat  /proc/devices|grep sbull
251 sbull

create device file:
mknod scull0 c 246 0
mknod pipe0  c 246 4
mknod sbulla b 251 0

step 3, create sock device with custom tcp server and client test program which invoke socket.
        it will create a socket file.

step 4, create erofs image using mkfs.erofs
step 5, mount erofs image and test the device file

1) scull 
echo test > scull0, you will get it by input 
cat scull0
test

2) sbull is the same to scull

3) pipe0

(1) input cat pipe0 at a shell
(2) input echo test > pip0 at another shell
So you will recive test string displayed at the fisrt shell terminal screen

4) socket
because erofs is a read only file system , socket file will not be created at fisrt running 
socket file need unlink fisrtly and recreate by program 
otherwise we got lots of string output at terminal when running socket server program.

Tks
Li GuiFu

-----????-----
???: Gaoxiang (OS) 
????: 2018?8?1? 16:18
???: liguifu (C) <bluce.liguifu at huawei.com>
??: Yuchao (T) <yuchao0 at huawei.com>; linux-erofs at lists.ozlabs.org; Wangzhigang (Brooke) <brooke.wangzhigang at hisilicon.com>
??: Re: [PATCH 08/11] erofs: support special inode

Hi Guifu,

On 2018/7/3 21:48, Chao Yu wrote:
>> The other code looks fine for me,
>> I think a basic test is needed for the function of this patch tho.
> 
> Yeah, I hope Guifu will leave the time for testing the patch.

Could you please reply this email with some test results of this patch?

Thanks,
Gao Xiang

  reply	other threads:[~2018-08-01  8:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  2:01 [PATCH 01/11] erofs: fix compile error Chao Yu
2018-06-22  2:01 ` [PATCH 02/11] erofs: fix to avoid potential overflow Chao Yu
2018-06-22  2:01 ` [PATCH 03/11] erofs: fix missing endian conversion Chao Yu
2018-06-22  2:01 ` [PATCH 04/11] erofs: fix to do endian conversion correctly Chao Yu
2018-06-22  2:01 ` [PATCH 05/11] erofs: fix to handle return value of erofs_init_page_bundle() correctly Chao Yu
2018-06-22  2:01 ` [PATCH 06/11] erofs: fix to return correct value of alloc_inode Chao Yu
2018-06-22  2:01 ` [PATCH 07/11] erofs: remove unused EROFS_XATTR_INDEX_ADVISE Chao Yu
2018-06-22  2:01 ` [PATCH 08/11] erofs: support special inode Chao Yu
2018-07-03  5:31   ` Gao Xiang
2018-07-03 13:48     ` Chao Yu
2018-08-01  8:17       ` Gao Xiang
2018-08-01  8:40         ` liguifu (C) [this message]
2018-06-22  2:01 ` [PATCH 09/11] erofs: introduce parse_options() Chao Yu
2018-06-22  2:01 ` [PATCH 10/11] erofs: introduce error injection infrastructure Chao Yu
2018-06-30 15:44   ` [PATCH v4] " Gao Xiang
2018-06-30 18:39   ` [PATCH v5] " Gao Xiang
2018-07-01  3:56     ` Chao Yu
2018-07-01  4:04       ` Gao Xiang
2018-06-22  2:01 ` [PATCH 11/11] erofs: support tracepoint Chao Yu
2018-07-03  9:44   ` Gao Xiang
2018-07-03 13:52     ` Chao Yu
2018-07-03 14:22       ` Gao Xiang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9156E5F840CEC74FB517F66C6FB59A33015789DA@dggemi525-mbx.china.huawei.com \
    --to=bluce.liguifu@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.