From: sebastian.capella@linaro.org (Sebastian Capella)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] init/do_mounts.c: ignore final \n in name_to_dev_t
Date: Tue, 28 Jan 2014 10:59:26 -0800 [thread overview]
Message-ID: <20140128185926.5312.36635@capellas-linux> (raw)
In-Reply-To: <20131022175414.14753.58063@capellas-linux>
Quoting Sebastian Capella (2013-10-22 10:54:14)
> Quoting Sebastian Capella (2013-10-10 10:50:10)
> > Quoting Sebastian Capella (2013-10-03 16:47:35)
> > > Quoting Sebastian Capella (2013-10-03 14:42:46)
> > > I looked into removing the const from the store function, but I'm not sure
> > > this is the right idea, so I'm going to shelf that for now.
> > >
> > Below are the three options considered thus far. Do
> > you have any additional suggestions or preferences?
> >
> > 1) copy buffer, remove \n.
> > - v1 patch did this
> > - alternatively could use an array on the stack or a preallocated global
> > Pros:
> > . cleanest change
> > . could use strim() proposed by Andrew
> > Cons:
> > . adds memcpy
> > 2) make name_to_dev_t work with readonly buffer to ignore \n
> > - v2 and v3 patches do this
> > Pros:
> > . no memcpy, no big modifications to unrelated code
> > Cons:
> > . seems more appropriate to harden store functions to user input
> > than name_to_dev_t.
> > . a little complicated
> > 3) remove const from buffer and modify contents in place to remove \n
> > - remove const from sysfs_ops.store, modify dependent definitions
> > - remove const from kobj_attribute.store, modify dependent definitions
> > Pros:
> > . no memcpy
> > Cons:
> > . a lot of modifications
> > . const contract to not modify the input buffer seems the right way.
>
> Hi Andrew,
>
> Do you have any feedback for me on this?
>
> I'm happy do make any changes you think are correct, but I'm unsure if
> you're asking me for option #3 above. It's quite an intrusive change,
> and changes old, established code and I'd like confirmation that's what
> you'd like before proceeding down that path.
>
> I've submitted patches with both options #1 and #2 above.
>
> Thanks,
>
> Sebastian
Ping.
Sorry for the lapse in attention to this.
Could you please clarify what is needed for this to be acceptable?
I'm a little confused about what is being asked of me.
Thanks!
Sebastian
next prev parent reply other threads:[~2014-01-28 18:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 21:10 [PATCH v3 0/2] PM / Hibernate: sysfs resume Sebastian Capella
2013-10-03 21:10 ` [PATCH v3 1/2] init/do_mounts.c: ignore final \n in name_to_dev_t Sebastian Capella
2013-10-03 21:15 ` Andrew Morton
2013-10-03 21:42 ` Sebastian Capella
2013-10-03 23:47 ` Sebastian Capella
2013-10-10 17:50 ` Sebastian Capella
2013-10-10 22:47 ` Eric W. Biederman
2013-10-10 23:39 ` Sebastian Capella
2013-10-22 17:54 ` Sebastian Capella
2014-01-28 18:59 ` Sebastian Capella [this message]
2014-01-28 20:54 ` Andrew Morton
2014-01-28 20:58 ` Sebastian Capella
2014-01-29 18:29 ` Sebastian Capella
2014-01-29 18:41 ` Andrew Morton
2013-10-03 21:10 ` [PATCH v3 2/2] PM / Hibernate: use name_to_dev_t to parse resume Sebastian Capella
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=20140128185926.5312.36635@capellas-linux \
--to=sebastian.capella@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).