public inbox for v9fs@lists.linux.dev
 help / color / mirror / Atom feed
From: syzbot <syzbot+62262fdc0e01d99573fc@syzkaller.appspotmail.com>
To: oleg@redhat.com
Cc: asmadeus@codewreck.org, brauner@kernel.org, dhowells@redhat.com,
	 ericvh@kernel.org, jack@suse.cz, jlayton@kernel.org,
	kprateek.nayak@amd.com,  linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,  linux_oss@crudebyte.com,
	lucho@ionkov.net, mjguzik@gmail.com,  netfs@lists.linux.dev,
	oleg@redhat.com, swapnil.sapkal@amd.com,
	 syzkaller-bugs@googlegroups.com, v9fs@lists.linux.dev,
	 viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [netfs?] INFO: task hung in netfs_unbuffered_write_iter
Date: Fri, 28 Mar 2025 06:07:16 -0700	[thread overview]
Message-ID: <67e69f04.050a0220.2f068f.0076.GAE@google.com> (raw)
In-Reply-To: <20250328130625.GA29527@redhat.com>

> On 03/28, K Prateek Nayak wrote:
>>
>> --- a/net/9p/trans_fd.c
>> +++ b/net/9p/trans_fd.c
>> @@ -687,7 +687,13 @@ static int p9_fd_request(struct p9_client *client, struct p9_req_t *req)
>>  	else
>>  		n = p9_fd_poll(m->client, NULL, NULL);
>> -	if (n & EPOLLOUT && !test_and_set_bit(Wworksched, &m->wsched))
>> +	/* Failed to send request */
>> +	if (!(n & EPOLLOUT)) {
>> +		p9_conn_cancel(m, -EIO);
>
> Thanks a lot Prateek!
>
> Can't really the changes in net/9p, but I am not sure. !(n & EPOLLOUT)
> means that pipe is full, nothing wrong. We need to kick m->rq in this
> case.
>
> Dominique says:
>
> 	For me the problem isn't so much that this gets ERESTARTSYS but that it
> 	nevers gets to read the 7 bytes that are available?
>
> Yes. Of course I do not pretend I fully understand the problem, but it
> seems this is because p9_read_work() doesn't set Rworksched and doesn't
> do schedule_work(&m->rq) if list_empty(&m->req_list).
>
> However, if the pipe is full, before the commit aaec5a95d59615523db0
> ("pipe_read: don't wake up the writer if the pipe is still full"),
> p9_read_work() -> p9_fd_read() -> kernel_read(ts->rd) triggered the
> unnecessary wakeup. This wakeup calls p9_pollwake() shich kicks
> p9_poll_workfn() -> p9_poll_mux(), and p9_poll_mux() will notice
> EPOLLIN and schedule_work(&m->rq).
>
> May be the patch below makes more sense?
>
> Oleg.
>
> #syz test: upstream

want either no args or 2 args (repo, branch), got 5

>
> diff --git a/net/9p/trans_fd.c b/net/9p/trans_fd.c
> index 56e62978e502..aa9cd248a243 100644
> --- a/net/9p/trans_fd.c
> +++ b/net/9p/trans_fd.c
> @@ -669,7 +669,6 @@ static void p9_poll_mux(struct p9_conn *m)
>  
>  static int p9_fd_request(struct p9_client *client, struct p9_req_t *req)
>  {
> -	__poll_t n;
>  	struct p9_trans_fd *ts = client->trans;
>  	struct p9_conn *m = &ts->conn;
>  
> @@ -687,13 +686,7 @@ static int p9_fd_request(struct p9_client *client, struct p9_req_t *req)
>  	list_add_tail(&req->req_list, &m->unsent_req_list);
>  	spin_unlock(&m->req_lock);
>  
> -	if (test_and_clear_bit(Wpending, &m->wsched))
> -		n = EPOLLOUT;
> -	else
> -		n = p9_fd_poll(m->client, NULL, NULL);
> -
> -	if (n & EPOLLOUT && !test_and_set_bit(Wworksched, &m->wsched))
> -		schedule_work(&m->wq);
> +	p9_poll_mux(m);
>  
>  	return 0;
>  }
>

  reply	other threads:[~2025-03-28 13:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250323184848.GB14883@redhat.com>
     [not found] ` <67e05e30.050a0220.21942d.0003.GAE@google.com>
     [not found]   ` <20250323194701.GC14883@redhat.com>
     [not found]     ` <CAGudoHHmvU54MU8dsZy422A4+ZzWTVs7LFevP7NpKzwZ1YOqgg@mail.gmail.com>
     [not found]       ` <20250323210251.GD14883@redhat.com>
     [not found]         ` <af0134a7-6f2a-46e1-85aa-c97477bd6ed8@amd.com>
     [not found]           ` <CAGudoHH9w8VO8069iKf_TsAjnfuRSrgiJ2e2D9-NGEDgXW+Lcw@mail.gmail.com>
     [not found]             ` <7e377feb-a78b-4055-88cc-2c20f924bf82@amd.com>
     [not found]               ` <f7585a27-aaef-4334-a1de-5e081f10c901@amd.com>
     [not found]                 ` <ff294b3c-cd24-4aa6-9d03-718ff7087158@amd.com>
2025-03-25 12:15                   ` [syzbot] [netfs?] INFO: task hung in netfs_unbuffered_write_iter Oleg Nesterov
2025-03-25 12:36                     ` Dominique Martinet
2025-03-25 13:04                     ` Oleg Nesterov
2025-03-25 14:49                       ` K Prateek Nayak
2025-03-25 14:58                         ` Dominique Martinet
2025-03-26 12:19                           ` Oleg Nesterov
2025-03-26 12:44                             ` Oleg Nesterov
2025-03-26 13:05                               ` Oleg Nesterov
2025-03-27 17:46                           ` K Prateek Nayak
2025-03-27 21:19                             ` syzbot
2025-03-27 22:18                               ` asmadeus
2025-03-28  4:01                                 ` K Prateek Nayak
2025-03-28  4:43                                   ` syzbot
2025-03-28 13:06                                   ` Oleg Nesterov
2025-03-28 13:07                                     ` syzbot [this message]
2025-03-28 13:25                                       ` Oleg Nesterov
2025-03-28 13:49                                         ` syzbot
2025-03-28 14:49                                           ` Oleg Nesterov
2025-03-28 15:22                                             ` syzbot
2025-03-28 17:00                                               ` Oleg Nesterov
2025-03-28 17:56                                                 ` K Prateek Nayak
2025-03-28 18:20                                                   ` Oleg Nesterov
2025-03-29  0:00                                                 ` asmadeus
2025-03-29 14:21                                                   ` Oleg Nesterov
2025-03-29 23:27                                                     ` asmadeus
2025-03-30 10:21                                                       ` Oleg Nesterov
     [not found] <67dedd2f.050a0220.31a16b.003f.GAE@google.com>
2025-08-03 12:09 ` 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=67e69f04.050a0220.2f068f.0076.GAE@google.com \
    --to=syzbot+62262fdc0e01d99573fc@syzkaller.appspotmail.com \
    --cc=asmadeus@codewreck.org \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=ericvh@kernel.org \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=mjguzik@gmail.com \
    --cc=netfs@lists.linux.dev \
    --cc=oleg@redhat.com \
    --cc=swapnil.sapkal@amd.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=v9fs@lists.linux.dev \
    --cc=viro@zeniv.linux.org.uk \
    /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