linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Cristian Rodríguez" <crrodriguez@opensuse.org>
To: linux-modules@vger.kernel.org
Cc: linux-modules <linux-modules@vger.kernel.org>
Subject: Re: [PATCH] RESEND: add missing O_CLOEXEC in kmod_module_get_size()
Date: Thu, 19 Jun 2014 17:45:08 -0400	[thread overview]
Message-ID: <53A359E4.8050906@opensuse.org> (raw)
In-Reply-To: <CAKi4VAKh6Z67OQekiSxm_aY1i7u1v1_PDNW8CxTQOrPqfKktMg@mail.gmail.com>

El jue 19 jun 2014 17:08:21 CLT, Lucas De Marchi escribió:
> On Wed, Jun 18, 2014 at 9:51 PM, Cristian Rodríguez
> <crrodriguez@opensuse.org> wrote:
>> ---
>>  libkmod/libkmod-module.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/libkmod/libkmod-module.c b/libkmod/libkmod-module.c
>> index 1d90f34..8046262 100644
>> --- a/libkmod/libkmod-module.c
>> +++ b/libkmod/libkmod-module.c
>> @@ -1781,7 +1781,7 @@ KMOD_EXPORT long kmod_module_get_size(const struct kmod_module *mod)
>>          * loaded.
>>          */
>>         snprintf(line, sizeof(line), "/sys/module/%s", mod->name);
>> -       dfd = open(line, O_RDONLY);
>> +       dfd = open(line, O_RDONLY|O_CLOEXEC);
>>         if (dfd < 0)
>>                 return -errno;
>>
>> --
>
> I don't know what's  the RESEND in the subject, but the patch looks
> good. I removed it and applied.
>
> Thanks.
>

That means I sent it before months ago but didn't get an answer and/or 
it applied.


--
Cristian
"I don't know the key to success, but the key to failure is trying to 
please everybody."

      reply	other threads:[~2014-06-19 21:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19  0:51 [PATCH] RESEND: add missing O_CLOEXEC in kmod_module_get_size() Cristian Rodríguez
2014-06-19 21:08 ` Lucas De Marchi
2014-06-19 21:45   ` Cristian Rodríguez [this message]

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=53A359E4.8050906@opensuse.org \
    --to=crrodriguez@opensuse.org \
    --cc=linux-modules@vger.kernel.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).