On Fri, Dec 18, 2020 at 8:11 AM Lai Jiangshan wrote:
>
> From: Lai Jiangshan
>
> 06249738a41a ("workqueue: Manually break affinity on hotplug")
> said that scheduler will not force break affinity for us.
>
> But workqueue highly depends on the old behavior. Many parts of the codes
> relies on it,
On Wed, Nov 25, 2020 at 2:11 AM Oleksandr Natalenko
wrote:
>
> Hello.
>
> On 25.11.2020 09:32, Greg Kroah-Hartman wrote:
> > On Tue, Nov 24, 2020 at 10:24:27PM +0100, Oleksandr Natalenko wrote:
> >> Hi.
> >>
> >> On 24.11.2020 15:23, Ard Biesheuvel wrote:
> >> > Surely caused by
> >> >
> >> > http
On Thu, Jul 16, 2020 at 7:47 AM Naresh Kamboju
wrote:
>
> On Sun, 12 Jul 2020 at 21:39, Paul E. McKenney wrote:
> >
> > On Sun, Jul 12, 2020 at 06:40:03PM +0530, madhuparnabhowmi...@gmail.com
> > wrote:
> > > From: Madhuparna Bhowmik
> > >
> > > Use hlist_for_each_entry_srcu() instead of hlist_
On Thu, Jun 4, 2020 at 6:06 AM Denis Efremov wrote:
>
> Use kzfree() instead of memset() with 0 followed by kfree().
>
> Signed-off-by: Denis Efremov
> ---
> drivers/scsi/storvsc_drv.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/scsi/storvsc_drv.c b/drive
On Mon, Sep 2, 2019 at 9:22 PM Qian Cai wrote:
>
> The linux-next commit "fs/namei.c: keep track of nd->root refcount status”
> [1] causes boot panic on all
> architectures here on today’s linux-next (0902). Reverted it will fix the
> issue.
I believe I'm seeing the same issue with next-2019090
On Sun, Jul 21, 2019 at 11:01 PM Ming Lei wrote:
>
> On Tue, Jun 18, 2019 at 4:57 AM Bart Van Assche wrote:
> >
> > On 6/17/19 5:19 AM, Christoph Hellwig wrote:
> > > We need to limit the devices max_sectors to what the DMA mapping
> > > implementation can support. If not we risk running out of
On Mon, Jun 3, 2019 at 7:37 AM Krzysztof Kozlowski wrote:
>
> On Mon, 3 Jun 2019 at 16:32, Stephen Rothwell wrote:
> >
> > Hi Krzysztof,
> >
> > On Mon, 3 Jun 2019 16:10:40 +0200 Krzysztof Kozlowski
> > wrote:
> > >
> > > Indeed it looks like effect of merge conflict resolution or applying.
> >
On Fri, May 31, 2019 at 10:00 AM Mike Kravetz wrote:
>
> On 5/30/19 7:41 PM, Huang, Ying wrote:
> > From: Huang Ying
> >
> > Mike reported the following warning messages
> >
> > get_swap_device: Bad swap file entry 1401
> >
> > This is produced by
> >
> > - total_swapcache_pages()
>
On Tue, Jan 8, 2019 at 4:49 PM Dan Williams wrote:
>
> On Tue, Jan 8, 2019 at 4:02 PM Dan Williams wrote:
> >
> > On Tue, Jan 8, 2019 at 3:55 PM Kees Cook wrote:
> > >
> > > On Tue, Jan 8, 2019 at 3:54 PM Dan Williams
> > > wrote:
> > > >
> > > > On Tue, Jan 8, 2019 at 3:34 PM Kees Cook wrote
On Thu, Jan 3, 2019 at 4:13 PM Haiyang Zhang wrote:
> > From: Adrian Vladu
> > Sent: Thursday, January 3, 2019 2:43 PM
> > To: linux-kernel@vger.kernel.org
> > Cc: Adrian Vladu ; KY Srinivasan
> > ; Haiyang Zhang ; Stephen
> > Hemminger ; Sasha Levin ;
> > David S. Miller ; apilotti
> >
> > Subj
On Thu, Jan 25, 2018 at 11:13 AM, Thomas Gleixner wrote:
> The simpler solution is to pull from tip x86/pti which is still 4.14 based
> and contains only the stuff which has to do with these issues. It's mostly
> in Linus tree already except for the topmost 3 patches.
>
> tglx
Found it:
On Wed, Jan 10, 2018 at 2:53 PM, Woodhouse, David wrote:
> On Thu, 2018-01-11 at 01:34 +0300, Alexey Dobriyan wrote:
>>
>> Bisection points to
>>
>> f3433c1010c6af61c9897f0f0447f81b991feac1 is the first bad commit
>> commit f3433c1010c6af61c9897f0f0447f81b991feac1
>> Author
12 matches
Mail list logo
