From: Jeff LaBundy <jeff@labundy.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org,
Benjamin Tissoires <bentiss@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/7] Input: rearrange input_alloc_device() to prepare for preallocating of vals
Date: Sun, 7 Jul 2024 14:56:06 -0500 [thread overview]
Message-ID: <Zory1pyXKbsvUFqU@nixie71> (raw)
In-Reply-To: <20240703213756.3375978-6-dmitry.torokhov@gmail.com>
Hi Dmitry,
On Wed, Jul 03, 2024 at 02:37:52PM -0700, Dmitry Torokhov wrote:
> In preparation to have dev->vals memory pre-allocated rearrange
> code in input_alloc_device() so that it allows handling multiple
> points of failure.
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Reviewed-by: Jeff LaBundy <jeff@labundy.com>
> ---
> drivers/input/input.c | 37 ++++++++++++++++++++++---------------
> 1 file changed, 22 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/input/input.c b/drivers/input/input.c
> index 40a04154f99d..9981fdfaee9f 100644
> --- a/drivers/input/input.c
> +++ b/drivers/input/input.c
> @@ -1982,21 +1982,28 @@ struct input_dev *input_allocate_device(void)
> struct input_dev *dev;
>
> dev = kzalloc(sizeof(*dev), GFP_KERNEL);
> - if (dev) {
> - dev->dev.type = &input_dev_type;
> - dev->dev.class = &input_class;
> - device_initialize(&dev->dev);
> - mutex_init(&dev->mutex);
> - spin_lock_init(&dev->event_lock);
> - timer_setup(&dev->timer, NULL, 0);
> - INIT_LIST_HEAD(&dev->h_list);
> - INIT_LIST_HEAD(&dev->node);
> -
> - dev_set_name(&dev->dev, "input%lu",
> - (unsigned long)atomic_inc_return(&input_no));
> -
> - __module_get(THIS_MODULE);
> - }
> + if (!dev)
> + return NULL;
> +
> + mutex_init(&dev->mutex);
> + spin_lock_init(&dev->event_lock);
> + timer_setup(&dev->timer, NULL, 0);
> + INIT_LIST_HEAD(&dev->h_list);
> + INIT_LIST_HEAD(&dev->node);
> +
> + dev->dev.type = &input_dev_type;
> + dev->dev.class = &input_class;
> + device_initialize(&dev->dev);
> + /*
> + * From this point on we can no longer simply "kfree(dev)", we need
> + * to use input_free_device() so that device core properly frees its
> + * resources associated with the input device.
> + */
> +
> + dev_set_name(&dev->dev, "input%lu",
> + (unsigned long)atomic_inc_return(&input_no));
> +
> + __module_get(THIS_MODULE);
>
> return dev;
> }
> --
> 2.45.2.803.g4e1b14247a-goog
>
Kind regards,
Jeff LaBundy
next prev parent reply other threads:[~2024-07-07 19:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 21:37 [PATCH v2 0/7] Simplify event handling logic in input core Dmitry Torokhov
2024-07-03 21:37 ` [PATCH v2 1/7] Input: evdev - remove ->event() method Dmitry Torokhov
2024-07-07 19:53 ` Jeff LaBundy
2024-07-03 21:37 ` [PATCH v2 2/7] Input: make sure input handlers define only one processing method Dmitry Torokhov
2024-07-07 19:53 ` Jeff LaBundy
2024-07-03 21:37 ` [PATCH v2 3/7] Input: make events() method return number of events processed Dmitry Torokhov
2024-07-07 19:54 ` Jeff LaBundy
2024-07-03 21:37 ` [PATCH v2 4/7] Input: simplify event handling logic Dmitry Torokhov
2024-07-07 19:55 ` Jeff LaBundy
2024-07-03 21:37 ` [PATCH v2 5/7] Input: rearrange input_alloc_device() to prepare for preallocating of vals Dmitry Torokhov
2024-07-07 19:56 ` Jeff LaBundy [this message]
2024-07-03 21:37 ` [PATCH v2 6/7] Input: preallocate memory to hold event values Dmitry Torokhov
2024-07-07 19:56 ` Jeff LaBundy
2024-07-03 21:37 ` [PATCH v2 7/7] Input: do not check number of events in input_pass_values() Dmitry Torokhov
2024-07-07 19:57 ` Jeff LaBundy
2024-07-04 6:44 ` [PATCH v2 0/7] Simplify event handling logic in input core Benjamin Tissoires
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=Zory1pyXKbsvUFqU@nixie71 \
--to=jeff@labundy.com \
--cc=bentiss@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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