From: Alison Schofield <amsfield22@gmail.com>
To: miguel.robles@farole.net
Cc: Daniel Baluta <daniel.baluta@gmail.com>,
linux-iio@vger.kernel.org, linux-iio-owner@vger.kernel.org
Subject: Re: PROBLEM: iio: dummy: Oops after mkdir
Date: Thu, 9 Mar 2017 09:40:49 -0800 [thread overview]
Message-ID: <20170309174049.GB3675@d830.WORKGROUP> (raw)
In-Reply-To: <20170309173653.GA3675@d830.WORKGROUP>
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
next prev parent reply other threads:[~2017-03-09 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2017-03-09 18:08 ` Miguel Robles
2017-03-09 18:15 ` Lars-Peter Clausen
2017-03-09 18:25 ` Miguel Robles
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=20170309174049.GB3675@d830.WORKGROUP \
--to=amsfield22@gmail.com \
--cc=daniel.baluta@gmail.com \
--cc=linux-iio-owner@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=miguel.robles@farole.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox