All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: syzbot <syzbot+3815dce0acab6c55984e@syzkaller.appspotmail.com>,
	Hillf Danton <hdanton@sina.com>,
	dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, netfs@lists.linux.dev,
	pc@manguebit.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfs?] INFO: task hung in vfs_utimes (3)
Date: Fri, 19 Sep 2025 22:25:53 +0900	[thread overview]
Message-ID: <aM1Z4aLfJZs4XydW@codewreck.org> (raw)
In-Reply-To: <20250919064800.GA20476@redhat.com>

Hi Oleg,

Oleg Nesterov wrote on Fri, Sep 19, 2025 at 08:48:00AM +0200:
> this is yet another issue seems to be fixed by
> 
> 	[PATCH] 9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN
> 	https://lore.kernel.org/all/20250819161013.GB11345@redhat.com/
> 
> are you going to apply it?

Sorry for the lack of reply, I had meant to deal with it earlier but
other patches came in and it fell into the cracks.

I've just pushed your patch to my -next branch, I'll submit it to Linus
during the merge window in a couple of weeks

-- 
Dominique Martinet | Asmadeus

  parent reply	other threads:[~2025-09-19 13:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 22:54 [syzbot] [netfs?] INFO: task hung in vfs_utimes (3) syzbot
2025-09-19  0:47 ` syzbot
2025-09-19  2:18   ` Hillf Danton
2025-09-19  2:44     ` syzbot
2025-09-19  7:14   ` Oleg Nesterov
2025-09-19  1:29 ` Forwarded: " syzbot
2025-09-19  6:48 ` Oleg Nesterov
2025-09-19 12:22   ` Hillf Danton
2025-09-19 13:25   ` Dominique Martinet [this message]
     [not found] <20250919012918.213435-1-lizhi.xu@windriver.com>
2025-09-19  2:04 ` syzbot

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=aM1Z4aLfJZs4XydW@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=dhowells@redhat.com \
    --cc=hdanton@sina.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfs@lists.linux.dev \
    --cc=oleg@redhat.com \
    --cc=pc@manguebit.org \
    --cc=syzbot+3815dce0acab6c55984e@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /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.