* PROBLEM: iio: dummy: Oops after mkdir
@ 2017-03-09 14:34 Miguel Robles
2017-03-09 15:41 ` Daniel Baluta
0 siblings, 1 reply; 8+ messages in thread
From: Miguel Robles @ 2017-03-09 14:34 UTC (permalink / raw)
To: linux-iio
Hello all,
I am beginning with Linux Kernel development. So I am trying to make
the IIO tasks posted on kernelnewbies DOT org.
But I got stuck with this problem that I am describing you hereafter
hoping that someone could bring me any feedback.
Many thanks,
Miguel ROBLES
----------
DESCRIPTION
-----------
After loading the corresponding IIO modules and mountig the configfs filesystem
I can not create an instance device with mkdir using the command:
$ sudo mkdir /config/iio/devices/dummy/my_dummy_device
Killed
I get the "Killed" message and looking at my syslog file, I got the warning
"refcount_t: increment on 0; use-after-free" followed by an "Oops" message.
When trying to execute the command one more time, the execution never finishes.
------
CONTEXT
-------
- Tried on 2 linux kernel releases:
- kernel: 4.10 (commit: 4977ab6)
- Kernel: 4.11 (commit: ec3b93a)
- Compiled with config file including the following options for IIO:
#
# IIO dummy driver
#
CONFIG_IIO_DUMMY_EVGEN=m
CONFIG_IIO_SIMPLE_DUMMY=m
CONFIG_IIO_SIMPLE_DUMMY_EVENTS=y
CONFIG_IIO_SIMPLE_DUMMY_BUFFER=y
CONFIG_IIO_CONFIGFS=m
- Modules loaded on following order:
/fs/configfs/configfs.ko
/drivers/iio/industrialio-configfs.ko
/drivers/iio/industrialio-sw-device.ko
/drivers/iio/industrialio-triggered-event.ko
/drivers/iio/dummy/iio_dummy_evgen.ko
/drivers/iio/dummy/iio_dummy.ko
-----
TRACE
-----
WARNING: CPU: 7 PID: 676 at lib/refcount.c:114 refcount_inc+0x37/0x40
refcount_t: increment on 0; use-after-free.
Modules linked in: iio_dummy(E) iio_dummy_evgen(E) industrialio_sw_device(E)
industrialio_configfs(E) configfs(E) binfmt_misc vmw_vsock_vmci_transport ...
CPU: 7 PID: 676 Comm: mkdir Tainted: G E 4.11.0-rc1+ #4
Call Trace:
dump_stack+0x63/0x90
__warn+0xcb/0xf0
warn_slowpath_fmt+0x5f/0x80
refcount_inc+0x37/0x40
config_item_get+0x1b/0x30 [configfs]
link_obj+0x42/0x50 [configfs]
link_group+0x19/0x70 [configfs]
configfs_mkdir+0x168/0x3d0 [configfs]
vfs_mkdir+0x10c/0x1b0
SyS_mkdir+0xd0/0x100
entry_SYSCALL_64_fastpath+0x1e/0xad
RIP: 0033:0x7f29650b33f7
RSP: 002b:00007ffcdd8babe8 EFLAGS: 00000206 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007ffcdd8baed8 RCX: 00007f29650b33f7
RDX: 0000000000000000 RSI: 00000000000001ff RDI: 00007ffcdd8bb82f
RBP: 0000000000000002 R08: 00000000000001ff R09: 0000000000402b00
R10: 00000000000001e5 R11: 0000000000000206 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
---[ end trace 71ffa6eaa306d186 ]---
BUG: unable to handle kernel paging request at ffffffffffffffb8
IP: link_obj+0x9/0x50 [configfs]
PGD 2d8e0c067
PUD 2d8e0e067
PMD 0
Oops: 0002 [#1] SMP
Modules linked in: iio_dummy(E) iio_dummy_evgen(E) industrialio_sw_device(E)
industrialio_con figfs(E) configfs(E) binfmt_misc vmw_vsock_vmci_transport ...
CPU: 7 PID: 676 Comm: mkdir Tainted: G W E 4.11.0-rc1+ #4
Hardware name: Gigabyte Technology Co., Ltd. Z170X-UD5 TH/Z170X-UD5 TH-CF, BIOS F2 09/04/2015
task: ffff9b5d4267e580 task.stack: ffffa71982eb8000
RIP: 0010:link_obj+0x9/0x50 [configfs]
RSP: 0018:ffffa71982ebbe10 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff9b5be8404250 RCX: 0000000000000006
RDX: 0000000000000000 RSI: ffffffffffffff88 RDI: ffff9b5be8404250
RBP: ffffa71982ebbe38 R08: 0000000000000001 R09: 00000000000003fe
R10: 0000000000000004 R11: 00000000000003fe R12: ffffffffffffff88
R13: ffff9b5be84042b8 R14: ffff9b5d7b53b540 R15: ffff9b5be8404250
FS: 00007f29657a8800(0000) GS:ffff9b5d91dc0000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffb8 CR3: 000000043fa94000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
? link_group+0x19/0x70 [configfs]
link_group+0x45/0x70 [configfs]
configfs_mkdir+0x168/0x3d0 [configfs]
vfs_mkdir+0x10c/0x1b0
SyS_mkdir+0xd0/0x100
entry_SYSCALL_64_fastpath+0x1e/0xad
RIP: 0033:0x7f29650b33f7
RSP: 002b:00007ffcdd8babe8 EFLAGS: 00000206 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007ffcdd8baed8 RCX: 00007f29650b33f7
RDX: 0000000000000000 RSI: 00000000000001ff RDI: 00007ffcdd8bb82f
RBP: 0000000000000002 R08: 00000000000001ff R09: 0000000000402b00
R10: 00000000000001e5 R11: 0000000000000206 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Code: 8b 7a 48 4c 89 ee e8 f7 fd ff ff 48 8b 73 48 41 89 c6 eb 87 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 85 ff <48> 89 7e 30 48 89 e5 53 48 89 f3 74 2f e8 a5 28 00 00 48 89 43
RIP: link_obj+0x9/0x50 [configfs] RSP: ffffa71982ebbe10
CR2: ffffffffffffffb8
---[ end trace 71ffa6eaa306d187 ]---
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: PROBLEM: iio: dummy: Oops after mkdir 2017-03-09 14:34 PROBLEM: iio: dummy: Oops after mkdir Miguel Robles @ 2017-03-09 15:41 ` Daniel Baluta 2017-03-09 15:59 ` miguel.robles 0 siblings, 1 reply; 8+ messages in thread From: Daniel Baluta @ 2017-03-09 15:41 UTC (permalink / raw) To: Miguel Robles; +Cc: linux-iio@vger.kernel.org On Thu, Mar 9, 2017 at 4:34 PM, Miguel Robles <miguel.robles@farole.net> wrote: > Hello all, > > I am beginning with Linux Kernel development. So I am trying to make > the IIO tasks posted on kernelnewbies DOT org. > But I got stuck with this problem that I am describing you hereafter > hoping that someone could bring me any feedback. > > Many thanks, > Miguel ROBLES > > ---------- > DESCRIPTION > ----------- > > After loading the corresponding IIO modules and mountig the configfs filesystem > I can not create an instance device with mkdir using the command: > > $ sudo mkdir /config/iio/devices/dummy/my_dummy_device > Killed > > I get the "Killed" message and looking at my syslog file, I got the warning > "refcount_t: increment on 0; use-after-free" followed by an "Oops" message. > When trying to execute the command one more time, the execution never finishes. > > > ------ > CONTEXT > ------- > > - Tried on 2 linux kernel releases: > - kernel: 4.10 (commit: 4977ab6) > - Kernel: 4.11 (commit: ec3b93a) > > - Compiled with config file including the following options for IIO: > > # > # IIO dummy driver > # > CONFIG_IIO_DUMMY_EVGEN=m > CONFIG_IIO_SIMPLE_DUMMY=m > CONFIG_IIO_SIMPLE_DUMMY_EVENTS=y > CONFIG_IIO_SIMPLE_DUMMY_BUFFER=y > > CONFIG_IIO_CONFIGFS=m Do you also have CONFIG_IIO_SW_DEVICE right? Will try to have a look at this asap. thanks, Daniel. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PROBLEM: iio: dummy: Oops after mkdir 2017-03-09 15:41 ` Daniel Baluta @ 2017-03-09 15:59 ` miguel.robles 2017-03-09 17:36 ` Alison Schofield 0 siblings, 1 reply; 8+ messages in thread From: miguel.robles @ 2017-03-09 15:59 UTC (permalink / raw) To: Daniel Baluta; +Cc: linux-iio, linux-iio-owner On 2017-03-09 16:41, Daniel Baluta wrote: > On Thu, Mar 9, 2017 at 4:34 PM, Miguel Robles > <miguel.robles@farole.net> wrote: >> Hello all, >> >> I am beginning with Linux Kernel development. So I am trying to make >> the IIO tasks posted on kernelnewbies DOT org. >> But I got stuck with this problem that I am describing you hereafter >> hoping that someone could bring me any feedback. >> >> Many thanks, >> Miguel ROBLES >> >> ---------- >> DESCRIPTION >> ----------- >> >> After loading the corresponding IIO modules and mountig the configfs >> filesystem >> I can not create an instance device with mkdir using the command: >> >> $ sudo mkdir /config/iio/devices/dummy/my_dummy_device >> Killed >> >> I get the "Killed" message and looking at my syslog file, I got the >> warning >> "refcount_t: increment on 0; use-after-free" followed by an "Oops" >> message. >> When trying to execute the command one more time, the execution never >> finishes. >> >> >> ------ >> CONTEXT >> ------- >> >> - Tried on 2 linux kernel releases: >> - kernel: 4.10 (commit: 4977ab6) >> - Kernel: 4.11 (commit: ec3b93a) >> >> - Compiled with config file including the following options for IIO: >> >> # >> # IIO dummy driver >> # >> CONFIG_IIO_DUMMY_EVGEN=m >> CONFIG_IIO_SIMPLE_DUMMY=m >> CONFIG_IIO_SIMPLE_DUMMY_EVENTS=y >> CONFIG_IIO_SIMPLE_DUMMY_BUFFER=y >> >> CONFIG_IIO_CONFIGFS=m > > Do you also have CONFIG_IIO_SW_DEVICE right? Yes, and the value is: CONFIG_IIO_SW_DEVICE=m. Thank you, Miguel > > Will try to have a look at this asap. > > > thanks, > Daniel. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PROBLEM: iio: dummy: Oops after mkdir 2017-03-09 15:59 ` miguel.robles @ 2017-03-09 17:36 ` Alison Schofield 2017-03-09 17:40 ` Alison Schofield 0 siblings, 1 reply; 8+ messages in thread From: Alison Schofield @ 2017-03-09 17:36 UTC (permalink / raw) To: miguel.robles; +Cc: Daniel Baluta, linux-iio, linux-iio-owner On Thu, Mar 09, 2017 at 04:59:39PM +0100, miguel.robles@farole.net wrote: > On 2017-03-09 16:41, Daniel Baluta wrote: > >On Thu, Mar 9, 2017 at 4:34 PM, Miguel Robles <miguel.robles@farole.net> > >wrote: > >>Hello all, > >> > >>I am beginning with Linux Kernel development. So I am trying to make > >>the IIO tasks posted on kernelnewbies DOT org. > >>But I got stuck with this problem that I am describing you hereafter > >>hoping that someone could bring me any feedback. > >> > >>Many thanks, > >>Miguel ROBLES > >> > >>---------- > >>DESCRIPTION > >>----------- > >> > >>After loading the corresponding IIO modules and mountig the configfs > >>filesystem > >>I can not create an instance device with mkdir using the command: > >> > >>$ sudo mkdir /config/iio/devices/dummy/my_dummy_device > >>Killed > >> > >>I get the "Killed" message and looking at my syslog file, I got the > >>warning > >>"refcount_t: increment on 0; use-after-free" followed by an "Oops" > >>message. > >>When trying to execute the command one more time, the execution never > >>finishes. > >> > >> > >>------ > >>CONTEXT > >>------- > >> > >>- Tried on 2 linux kernel releases: > >> - kernel: 4.10 (commit: 4977ab6) > >> - Kernel: 4.11 (commit: ec3b93a) > >> > >>- Compiled with config file including the following options for IIO: > >> > >># > >># IIO dummy driver > >># > >>CONFIG_IIO_DUMMY_EVGEN=m > >>CONFIG_IIO_SIMPLE_DUMMY=m > >>CONFIG_IIO_SIMPLE_DUMMY_EVENTS=y > >>CONFIG_IIO_SIMPLE_DUMMY_BUFFER=y > >> > >>CONFIG_IIO_CONFIGFS=m > > > >Do you also have CONFIG_IIO_SW_DEVICE right? > > Yes, and the value is: CONFIG_IIO_SW_DEVICE=m. > > Thank you, > Miguel > > > >Will try to have a look at this asap. > > > > > >thanks, > >Daniel. Daniel, You probably saw, but just in case... I verified that the process, including the above mkdir, is working on 4.10-rc3. (So, I'm relieved the Outreachy applicants won't start hitting it.) alisons > -- > To unsubscribe from this list: send the line "unsubscribe linux-iio" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PROBLEM: iio: dummy: Oops after mkdir 2017-03-09 17:36 ` Alison Schofield @ 2017-03-09 17:40 ` Alison Schofield 2017-03-09 18:08 ` Miguel Robles 0 siblings, 1 reply; 8+ messages in thread From: Alison Schofield @ 2017-03-09 17:40 UTC (permalink / raw) To: miguel.robles; +Cc: Daniel Baluta, linux-iio, linux-iio-owner On Thu, Mar 09, 2017 at 09:36:54AM -0800, Alison Schofield wrote: > On Thu, Mar 09, 2017 at 04:59:39PM +0100, miguel.robles@farole.net wrote: > > On 2017-03-09 16:41, Daniel Baluta wrote: > > >On Thu, Mar 9, 2017 at 4:34 PM, Miguel Robles <miguel.robles@farole.net> > > >wrote: > > >>Hello all, > > >> > > >>I am beginning with Linux Kernel development. So I am trying to make > > >>the IIO tasks posted on kernelnewbies DOT org. > > >>But I got stuck with this problem that I am describing you hereafter > > >>hoping that someone could bring me any feedback. > > >> > > >>Many thanks, > > >>Miguel ROBLES > > >> > > >>---------- > > >>DESCRIPTION > > >>----------- > > >> > > >>After loading the corresponding IIO modules and mountig the configfs > > >>filesystem > > >>I can not create an instance device with mkdir using the command: > > >> > > >>$ sudo mkdir /config/iio/devices/dummy/my_dummy_device > > >>Killed > > >> > > >>I get the "Killed" message and looking at my syslog file, I got the > > >>warning > > >>"refcount_t: increment on 0; use-after-free" followed by an "Oops" > > >>message. > > >>When trying to execute the command one more time, the execution never > > >>finishes. > > >> > > >> > > >>------ > > >>CONTEXT > > >>------- > > >> > > >>- Tried on 2 linux kernel releases: > > >> - kernel: 4.10 (commit: 4977ab6) > > >> - Kernel: 4.11 (commit: ec3b93a) > > >> > > >>- Compiled with config file including the following options for IIO: > > >> > > >># > > >># IIO dummy driver > > >># > > >>CONFIG_IIO_DUMMY_EVGEN=m > > >>CONFIG_IIO_SIMPLE_DUMMY=m > > >>CONFIG_IIO_SIMPLE_DUMMY_EVENTS=y > > >>CONFIG_IIO_SIMPLE_DUMMY_BUFFER=y > > >> > > >>CONFIG_IIO_CONFIGFS=m > > > > > >Do you also have CONFIG_IIO_SW_DEVICE right? > > > > Yes, and the value is: CONFIG_IIO_SW_DEVICE=m. > > > > Thank you, > > Miguel > > > > > >Will try to have a look at this asap. > > > > > > > > >thanks, > > >Daniel. > > Daniel, > You probably saw, but just in case... > I verified that the process, including the above mkdir, is working on > 4.10-rc3. (So, I'm relieved the Outreachy applicants won't start > hitting it.) > alisons I see Lars' patch! It worked for me because I used CONFIG_IIO_CONFIGFS built-in. alisons > > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-iio" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PROBLEM: iio: dummy: Oops after mkdir 2017-03-09 17:40 ` Alison Schofield @ 2017-03-09 18:08 ` Miguel Robles 2017-03-09 18:15 ` Lars-Peter Clausen 0 siblings, 1 reply; 8+ messages in thread From: Miguel Robles @ 2017-03-09 18:08 UTC (permalink / raw) To: Alison Schofield; +Cc: Daniel Baluta, linux-iio, linux-iio-owner On Thu, Mar 09, 2017 at 09:40:49AM -0800, Alison Schofield wrote: > On Thu, Mar 09, 2017 at 09:36:54AM -0800, Alison Schofield wrote: > > On Thu, Mar 09, 2017 at 04:59:39PM +0100, miguel.robles@farole.net wrote: > > > On 2017-03-09 16:41, Daniel Baluta wrote: > > > >On Thu, Mar 9, 2017 at 4:34 PM, Miguel Robles <miguel.robles@farole.net> > > > >wrote: > > > >>Hello all, > > > >> > > > >>I am beginning with Linux Kernel development. So I am trying to make > > > >>the IIO tasks posted on kernelnewbies DOT org. > > > >>But I got stuck with this problem that I am describing you hereafter > > > >>hoping that someone could bring me any feedback. > > > >> > > > >>Many thanks, > > > >>Miguel ROBLES > > > >> > > > >>---------- > > > >>DESCRIPTION > > > >>----------- > > > >> > > > >>After loading the corresponding IIO modules and mountig the configfs > > > >>filesystem > > > >>I can not create an instance device with mkdir using the command: > > > >> > > > >>$ sudo mkdir /config/iio/devices/dummy/my_dummy_device > > > >>Killed > > > >> > > > >>I get the "Killed" message and looking at my syslog file, I got the > > > >>warning > > > >>"refcount_t: increment on 0; use-after-free" followed by an "Oops" > > > >>message. > > > >>When trying to execute the command one more time, the execution never > > > >>finishes. > > > >> > > > >> > > > >>------ > > > >>CONTEXT > > > >>------- > > > >> > > > >>- Tried on 2 linux kernel releases: > > > >> - kernel: 4.10 (commit: 4977ab6) > > > >> - Kernel: 4.11 (commit: ec3b93a) > > > >> > > > >>- Compiled with config file including the following options for IIO: > > > >> > > > >># > > > >># IIO dummy driver > > > >># > > > >>CONFIG_IIO_DUMMY_EVGEN=m > > > >>CONFIG_IIO_SIMPLE_DUMMY=m > > > >>CONFIG_IIO_SIMPLE_DUMMY_EVENTS=y > > > >>CONFIG_IIO_SIMPLE_DUMMY_BUFFER=y > > > >> > > > >>CONFIG_IIO_CONFIGFS=m > > > > > > > >Do you also have CONFIG_IIO_SW_DEVICE right? > > > > > > Yes, and the value is: CONFIG_IIO_SW_DEVICE=m. > > > > > > Thank you, > > > Miguel > > > > > > > >Will try to have a look at this asap. > > > > > > > > > > > >thanks, > > > >Daniel. > > > > Daniel, > > You probably saw, but just in case... > > I verified that the process, including the above mkdir, is working on > > 4.10-rc3. (So, I'm relieved the Outreachy applicants won't start > > hitting it.) > > alisons > > I see Lars' patch! > It worked for me because I used CONFIG_IIO_CONFIGFS built-in. > alisons > I applied Lar's patch and now the command is working fine! Even if I do not understand very well the patch. I mean, I always declared CONFIG_IIO_CONFIGFS, so the code should be normally always compiled. Miguel > > > > > > > > > -- > > > To unsubscribe from this list: send the line "unsubscribe linux-iio" in > > > the body of a message to majordomo@vger.kernel.org > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-iio" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PROBLEM: iio: dummy: Oops after mkdir 2017-03-09 18:08 ` Miguel Robles @ 2017-03-09 18:15 ` Lars-Peter Clausen 2017-03-09 18:25 ` Miguel Robles 0 siblings, 1 reply; 8+ messages in thread From: Lars-Peter Clausen @ 2017-03-09 18:15 UTC (permalink / raw) To: Miguel Robles, Alison Schofield; +Cc: Daniel Baluta, linux-iio, linux-iio-owner On 03/09/2017 07:08 PM, Miguel Robles wrote: > On Thu, Mar 09, 2017 at 09:40:49AM -0800, Alison Schofield wrote: >> On Thu, Mar 09, 2017 at 09:36:54AM -0800, Alison Schofield wrote: >>> On Thu, Mar 09, 2017 at 04:59:39PM +0100, miguel.robles@farole.net wrote: >>>> On 2017-03-09 16:41, Daniel Baluta wrote: >>>>> On Thu, Mar 9, 2017 at 4:34 PM, Miguel Robles <miguel.robles@farole.net> >>>>> wrote: >>>>>> Hello all, [...] >>>>>> CONFIG_IIO_CONFIGFS=m >>>>> >>>>> Do you also have CONFIG_IIO_SW_DEVICE right? >>>> >>>> Yes, and the value is: CONFIG_IIO_SW_DEVICE=m. >>>> >>>> Thank you, >>>> Miguel >>>>> >>>>> Will try to have a look at this asap. >>>>> >>>>> >>>>> thanks, >>>>> Daniel. >>> >>> Daniel, >>> You probably saw, but just in case... >>> I verified that the process, including the above mkdir, is working on >>> 4.10-rc3. (So, I'm relieved the Outreachy applicants won't start >>> hitting it.) >>> alisons >> >> I see Lars' patch! >> It worked for me because I used CONFIG_IIO_CONFIGFS built-in. >> alisons >> > I applied Lar's patch and now the command is working fine! > Even if I do not understand very well the patch. I mean, I always declared > CONFIG_IIO_CONFIGFS, so the code should be normally always compiled. What the kernel build system does is when the symbol is select as built-in (=y) it does `#define CONFIG_CONFIGFS_FS`. When the symbol is selected as a module (=m) it does `#define CONFIG_CONFIGFS_FS_MODULE`. The IS_ENABLED() macro basically checks for both and evaluates to true if either of them is defined. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: PROBLEM: iio: dummy: Oops after mkdir 2017-03-09 18:15 ` Lars-Peter Clausen @ 2017-03-09 18:25 ` Miguel Robles 0 siblings, 0 replies; 8+ messages in thread From: Miguel Robles @ 2017-03-09 18:25 UTC (permalink / raw) To: Lars-Peter Clausen Cc: Alison Schofield, Daniel Baluta, linux-iio, linux-iio-owner On Thu, Mar 09, 2017 at 07:15:54PM +0100, Lars-Peter Clausen wrote: > On 03/09/2017 07:08 PM, Miguel Robles wrote: > > On Thu, Mar 09, 2017 at 09:40:49AM -0800, Alison Schofield wrote: > >> On Thu, Mar 09, 2017 at 09:36:54AM -0800, Alison Schofield wrote: > >>> On Thu, Mar 09, 2017 at 04:59:39PM +0100, miguel.robles@farole.net wrote: > >>>> On 2017-03-09 16:41, Daniel Baluta wrote: > >>>>> On Thu, Mar 9, 2017 at 4:34 PM, Miguel Robles <miguel.robles@farole.net> > >>>>> wrote: > >>>>>> Hello all, > [...] > >>>>>> CONFIG_IIO_CONFIGFS=m > >>>>> > >>>>> Do you also have CONFIG_IIO_SW_DEVICE right? > >>>> > >>>> Yes, and the value is: CONFIG_IIO_SW_DEVICE=m. > >>>> > >>>> Thank you, > >>>> Miguel > >>>>> > >>>>> Will try to have a look at this asap. > >>>>> > >>>>> > >>>>> thanks, > >>>>> Daniel. > >>> > >>> Daniel, > >>> You probably saw, but just in case... > >>> I verified that the process, including the above mkdir, is working on > >>> 4.10-rc3. (So, I'm relieved the Outreachy applicants won't start > >>> hitting it.) > >>> alisons > >> > >> I see Lars' patch! > >> It worked for me because I used CONFIG_IIO_CONFIGFS built-in. > >> alisons > >> > > I applied Lar's patch and now the command is working fine! > > Even if I do not understand very well the patch. I mean, I always declared > > CONFIG_IIO_CONFIGFS, so the code should be normally always compiled. > > What the kernel build system does is when the symbol is select as built-in > (=y) it does `#define CONFIG_CONFIGFS_FS`. When the symbol is selected as a > module (=m) it does `#define CONFIG_CONFIGFS_FS_MODULE`. The IS_ENABLED() > macro basically checks for both and evaluates to true if either of them is > defined. > Now I undestand :). Thank you for your clear explanation. Miguel ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2017-03-09 18:47 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2017-03-09 14:34 PROBLEM: iio: dummy: Oops after mkdir Miguel Robles 2017-03-09 15:41 ` Daniel Baluta 2017-03-09 15:59 ` miguel.robles 2017-03-09 17:36 ` Alison Schofield 2017-03-09 17:40 ` Alison Schofield 2017-03-09 18:08 ` Miguel Robles 2017-03-09 18:15 ` Lars-Peter Clausen 2017-03-09 18:25 ` Miguel Robles
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox