public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Marco Elver <elver@google.com>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	syzbot <syzbot+5f47a8cea6a12b77a876@syzkaller.appspotmail.com>
Subject: Re: [syzbot] BUG: sleeping function called from invalid context in __might_resched
Date: Fri, 12 Nov 2021 18:15:44 +0100	[thread overview]
Message-ID: <4117061.qmFDOAJpEW@localhost.localdomain> (raw)
In-Reply-To: <YY6WB9wMx/0VaqDx@elver.google.com>

On Friday, November 12, 2021 5:27:51 PM CET Marco Elver wrote:

> My guess is that in this case '!preemptible()' could work:
> 
> 	#define preemptible()	(preempt_count() == 0 && !
irqs_disabled())
> 
> But still am not entirely sure.
> 
> Thanks,
> -- Marco

Oh, I didn't even know that we have that preemptible() macro. 

Instead, I should have known that in_atomic() won't do, since last week I had 
copy-pasted in an email that I sent to someone on the LKML exactly the same 
inline documentation that you have showed now.

Thanks, Marco. At least, this thread was useful to make me recall how these 
macros should be used :)

Regards,

Fabio





  reply	other threads:[~2021-11-12 17:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 10:18 [syzbot] BUG: sleeping function called from invalid context in __might_resched syzbot
2021-11-12 12:22 ` Fabio M. De Francesco
2021-11-12 13:58   ` Marco Elver
2021-11-12 16:05     ` Fabio M. De Francesco
2021-11-12 16:27       ` Marco Elver
2021-11-12 17:15         ` Fabio M. De Francesco [this message]
2021-11-13 20:13 ` syzbot
2021-11-16  7:57   ` Fabio M. De Francesco
2021-11-16  8:09     ` syzbot
2021-11-16  8:53       ` Fabio M. De Francesco
2021-11-16  8:55         ` syzbot
2021-11-16  9:03         ` Fabio M. De Francesco
2021-11-16  9:03           ` syzbot
2021-11-16  9:20           ` syzbot
2021-11-16  9:13         ` Fabio M. De Francesco
2021-11-16  9:38           ` syzbot
2021-11-16 10:24     ` Marco Elver
2021-11-16 11:35       ` Fabio M. De Francesco

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=4117061.qmFDOAJpEW@localhost.localdomain \
    --to=fmdefrancesco@gmail.com \
    --cc=elver@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+5f47a8cea6a12b77a876@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox