All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: brgl@bgdev.pl
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	akpm@linux-foundation.org, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v4] gpio: sim: fix an invalid __free() usage
Date: Tue, 19 Sep 2023 15:37:17 +0800	[thread overview]
Message-ID: <ZQlPre4nnydZyDAm@sol> (raw)
In-Reply-To: <CAMRc=MfkzdFgwEuNGJYgxyCA_b__Ds-jA4S+jVT1ULJ9DTRhOw@mail.gmail.com>

On Tue, Sep 19, 2023 at 12:31:36AM -0700, brgl@bgdev.pl wrote:
> On Mon, 18 Sep 2023 17:31:36 +0200, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> said:
> > On Mon, Sep 18, 2023 at 04:55:33PM +0200, Bartosz Golaszewski wrote:
> >> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> >>
> >> gpio_sim_make_line_names() returns NULL or ERR_PTR() so we must not use
> >> __free(kfree) on the returned address. Split this function into two, one
> >> that determines the size of the "gpio-line-names" array to allocate and
> >> one that actually sets the names at correct offsets. The allocation and
> >> assignment of the managed pointer happens in between.
> >
> > ...
> >
> >> +	unsigned int size = 0;
> >>
> >>  	list_for_each_entry(line, &bank->line_list, siblings) {
> >> +		if (!line->name || (line->offset >= bank->num_lines))
> >>  			continue;
> >>
> >> +		size = line->offset + 1;
> >>  	}
> >>
> >> +	return size;
> >
> > So, now the function iterates over all lines and returns the size of the last
> > match, correct?
> >
> > Why not
> >
> > 	list_for_each_entry_reversed() {
> > 		if (line->name && ())
> > 			break;
> > 	}
> >
> > 	return size;
> >
> > ?
> 
> Because the line objects are not sorted by offset. They are added at the end
> of the list in the order the user creates their corresponding configfs groups.
> 

Then your patch is also broken as it uses the last named entry,
not the named entry with the greatest offset??

Cheers,
Kent.

  reply	other threads:[~2023-09-19  7:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 14:55 [PATCH v4] gpio: sim: fix an invalid __free() usage Bartosz Golaszewski
2023-09-18 15:31 ` Andy Shevchenko
2023-09-19  7:31   ` brgl
2023-09-19  7:37     ` Kent Gibson [this message]
2023-09-19  7:46       ` brgl
2023-09-19 10:49     ` Andy Shevchenko
2023-09-23 18:19       ` Linus Torvalds
2023-09-25  6:58         ` Andy Shevchenko

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=ZQlPre4nnydZyDAm@sol \
    --to=warthog618@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.