netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>, Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, geliang@kernel.org, horms@kernel.org,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	martineau@kernel.org, mptcp@lists.linux.dev,
	netdev@vger.kernel.org, pabeni@redhat.com,
	syzkaller-bugs@googlegroups.com,
	syzbot <syzbot+e364f774c6f57f2c86d1@syzkaller.appspotmail.com>
Subject: Re: [syzbot] [mptcp?] general protection fault in proc_scheduler
Date: Sat, 4 Jan 2025 20:11:49 +0100	[thread overview]
Message-ID: <89c2208c-fe23-43eb-89ef-876e55731a50@kernel.org> (raw)
In-Reply-To: <20250104190010.GF1977892@ZenIV>

Hi Al, Eric,

On 04/01/2025 20:00, Al Viro wrote:
> On Sat, Jan 04, 2025 at 07:53:22PM +0100, Eric Dumazet wrote:
> 
>> I do think this is a bug in process accounting, not in networking.
>>
>> It might make sense to output a record on a regular file, but probably
>> not on any other files.
>>
>> diff --git a/kernel/acct.c b/kernel/acct.c
>> index 179848ad33e978a557ce695a0d6020aa169177c6..a211305cb930f6860d02de7f45ebd260ae03a604
>> 100644
>> --- a/kernel/acct.c
>> +++ b/kernel/acct.c
>> @@ -495,6 +495,9 @@ static void do_acct_process(struct bsd_acct_struct *acct)
>>         const struct cred *orig_cred;
>>         struct file *file = acct->file;
>>
>> +       if (S_ISREG(file_inode(file)->i_mode))
>> +               return;
> 
> ... won't help, since the file in question *is* a regular file.  IOW, it's
> a wrong predicate here.

On my side, it looks like I'm not able to reproduce the issue with this
patch. Without it, it is very easy to reproduce it. (But I don't know if
there are other consequences that would avoid the issue to happen: when
looking at the logs, with the patch, I don't have heaps of "Process
accounting resumed" messages that I had before.)

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2025-01-04 19:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 14:12 [syzbot] [mptcp?] general protection fault in proc_scheduler syzbot
2025-01-02 15:21 ` Eric Dumazet
2025-01-04 18:38   ` Matthieu Baerts
2025-01-04 18:53     ` Eric Dumazet
2025-01-04 19:00       ` Al Viro
2025-01-04 19:11         ` Matthieu Baerts [this message]
2025-01-04 20:21           ` Al Viro
2025-01-05  8:32             ` Eric Dumazet
2025-01-05 11:29               ` Al Viro
2025-01-05 16:52                 ` Eric Dumazet
2025-01-05 17:03                   ` Matthieu Baerts
2025-01-05 19:54                   ` Al Viro
2025-01-05 20:50                     ` Al Viro
2025-01-05 21:11                       ` Al Viro
2025-01-05 17:03             ` Matthieu Baerts
2025-01-04 19:11       ` Matthieu Baerts
2025-01-06 13:32         ` Joel Granados
2025-01-06 14:27           ` Matthieu Baerts
2025-01-06 15:27             ` Eric Dumazet
2025-01-06 15:34               ` Matthieu Baerts
2025-01-08 14:37             ` Joel Granados
2025-01-04 20:09       ` Al Viro

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=89c2208c-fe23-43eb-89ef-876e55731a50@kernel.org \
    --to=matttbe@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+e364f774c6f57f2c86d1@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --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;
as well as URLs for NNTP newsgroup(s).