Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1634351
| From | Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] m501fb: don't return zero on failure path in sm501fb_start() |
| Date | 2017-05-02 13:40 +0200 |
| Message-ID | <tCEjT-67E-3@gated-at.bofh.it> (permalink) |
| References | <tCEjT-67E-5@gated-at.bofh.it> <tBGnN-1QW-37@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Saturday, April 29, 2017 09:33:39 PM Alexey Khoroshilov wrote: > If fbmem iomemory mapping failed, sm501fb_start() breaks off > initialization, deallocates resources, but returns zero. > As a result, double deallocation can happen in sm501fb_stop(). > > Found by Linux Driver Verification project (linuxtesting.org). > > Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru> Patch queued for 4.12, thanks. Best regards, -- Bartlomiej Zolnierkiewicz Samsung R&D Institute Poland Samsung Electronics
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH] m501fb: don't return zero on failure path in sm501fb_start() Alexey Khoroshilov <khoroshilov@ispras.ru> - 2017-04-29 21:40 +0200 Re: [PATCH] m501fb: don't return zero on failure path in sm501fb_start() Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> - 2017-05-02 13:40 +0200
csiph-web