Re: PROBLEM: iio: dummy: Oops after mkdir

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx wrote:
> > > On 2017-03-09 16:41, Daniel Baluta wrote:
> > > >On Thu, Mar 9, 2017 at 4:34 PM, Miguel Robles <miguel.robles@xxxxxxxxxx>
> > > >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@xxxxxxxxxxxxxxx
> > > 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@xxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Input]     [Linux Kernel]     [Linux SCSI]     [X.org]

  Powered by Linux