From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Khadija Kamran <kamrankhadijadj@gmail.com>
Cc: outreachy@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8] staging: axis-fifo: initialize timeouts in init only
Date: Mon, 20 Mar 2023 14:38:24 +0100 [thread overview]
Message-ID: <3180435.l52yBJDM9G@suse> (raw)
In-Reply-To: <ZBf+XDN8GM0xDDCq@khadija-virtual-machine>
On lunedì 20 marzo 2023 07:34:04 CET Khadija Kamran wrote:
> On Fri, Mar 17, 2023 at 11:29:25AM +0100, Fabio M. De Francesco wrote:
> > Khadija,
> >
> > Congratulations for having your first patch in Linux, via Greg's staging
> > tree.
> >
> > It will take some time before it reaches mainline, although it is already
on
> > its way to get upstream.
>
> Thank you! :)
>
> > On giovedì 16 marzo 2023 21:09:00 CET Khadija Kamran wrote:
> > > Initialize the module parameters, read_timeout and write_timeout once in
> > > init().
> > >
> > > Module parameters can only be set once and cannot be modified later, so
we
> > > don't need to evaluate them again when passing the parameters to
> > > wait_event_interruptible_timeout().
> >
> > Greg made you (and indirectly me notice) that the statement above is a
kind
> > of short-circuit because it misses to make the readers notice that you are
> > dealing with specific permissions granted to these two module's
parameters.
> >
> > Please take a look at the permissions associated with those parameters:
> >
> > module_param(write_timeout, long, 0444);
> > module_param(read_timeout, long, 0444);
> >
> > Can you understand what '0444' stands for? What if their permissions were
> > instead something like '0666' or '0664'?
>
> Hey Fabio!
>
> I understand that 0444 shows read permissions only.
Yes, correct.
Only "read" permissions for owner, group, others.
Obviously, when the module is initialized, "insmod" can pass actual values to
the arguments. The point is that from that moment onward nobody is allowed to
change the initial values associated with this variables, but they can still
be read at will.
> I am trying to make sense of this. As the permissions do not allow
> write, so the value cannot be configured afterwards.
Yes, if with "afterwards" you are intending after they are set at insmod runs.
> Instead of saying 'cannot be modified later', we should talk more about
> permissions here too.
I'm confused by this statement. Can you please rephrase?
> Am I getting it right?
Not sure, it depends on what you meant with the previous phrase.
> Thank you!
>
> Regards,
> Khadija
You're welcome!
So, thanks for working on this patch as long as it takes to get it done.
I think the lesson to be learned is that in our community there are barriers
to the entry of substandard products and therefore people have to do their
best if they really want to see their work applied.
These tasks are not for the "faints of heart" :-)
Fabio
next prev parent reply other threads:[~2023-03-20 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 20:09 [PATCH v8] staging: axis-fifo: initialize timeouts in init only Khadija Kamran
2023-03-17 7:13 ` Greg Kroah-Hartman
2023-03-17 8:58 ` Fabio M. De Francesco
2023-03-20 6:17 ` Khadija Kamran
2023-03-20 6:09 ` Khadija Kamran
2023-03-17 10:29 ` Fabio M. De Francesco
2023-03-20 6:34 ` Khadija Kamran
2023-03-20 13:38 ` Fabio M. De Francesco [this message]
2023-03-20 14:36 ` Khadija Kamran
2023-03-20 16:55 ` Fabio M. De Francesco
2023-03-20 17:05 ` Khadija Kamran
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=3180435.l52yBJDM9G@suse \
--to=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kamrankhadijadj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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