linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Jason Gunthorpe <jgg@nvidia.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Harry Yoo <harry.yoo@oracle.com>,
	David Rientjes <rientjes@google.com>,
	Christoph Lameter <cl@gentwo.org>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	Pedro Falcato <pfalcato@suse.de>,
	Bernard Metzler <bernard.metzler@linux.dev>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	David Howells <dhowells@redhat.com>
Subject: Re: [GIT PULL] slab updates for 6.17
Date: Wed, 30 Jul 2025 20:50:58 +0200	[thread overview]
Message-ID: <b05d424b-fa55-4e12-a1af-7504b1be20a6@suse.cz> (raw)
In-Reply-To: <20250730184724.GC89283@nvidia.com>

On 7/30/25 20:47, Jason Gunthorpe wrote:
> On Wed, Jul 30, 2025 at 11:42:21AM -0700, Linus Torvalds wrote:
>> On Mon, 28 Jul 2025 at 09:56, Vlastimil Babka <vbabka@suse.cz> wrote:
>> >
>> > We've hit a last-minute snag last week when lkp reported [1] the commit
>> > "mm, slab: use frozen pages for large kmalloc" exposed a pre-existing bug
>> > in siw_tcp_sendpages(). Pedro has been fixing it [2] so hopefully that will
>> > result in a PR soon, which you can pull before this one - or perhaps take
>> > the fix directly. If that gets stuck for some reason and taking the fix
>> > later would be unacceptable, I can do another PR with my commit taken out.
>> >
>> > [1] https://lore.kernel.org/all/202507220801.50a7210-lkp@intel.com/
>> > [2] https://lore.kernel.org/all/20250723104123.190518-1-pfalcato@suse.de/
>> 
>> Thanks for the heads up.
>> 
>> I've pulled this, although I don't see the rdma fix in the rdma tree

Thanks.

>> (the pull for which is still pending in my inbox - I've merged a big
>> chunk already, people have been very good about sending their pulls
>> early - thanks)
> 
> It is not there, it was unclear in the emails what should happen and I
> did not want to delay things due to your travel note.
> 
>> I'll take the fix directly in the worst case, but prefer for things to
>> go through the normal subsystem maintainer if at all possible, and
>> this one seems fairly straightforward.
> 
> I think it will be easiest for all if I send a one patch PR after you pick up
> the main RDMA PR in the next few days. siw is not so critical that we
> need to rush.

Great, thanks. The last version with ack from Bernard is here:

https://lore.kernel.org/all/20250729120348.495568-1-pfalcato@suse.de/

> Thanks,
> Jason



  reply	other threads:[~2025-07-30 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 16:56 Vlastimil Babka
2025-07-30 18:42 ` Linus Torvalds
2025-07-30 18:47   ` Jason Gunthorpe
2025-07-30 18:50     ` Vlastimil Babka [this message]
2025-07-30 18:52     ` Linus Torvalds
2025-07-30 18:47 ` pr-tracker-bot

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=b05d424b-fa55-4e12-a1af-7504b1be20a6@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=bernard.metzler@linux.dev \
    --cc=cl@gentwo.org \
    --cc=dhowells@redhat.com \
    --cc=harry.yoo@oracle.com \
    --cc=jgg@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=pfalcato@suse.de \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.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