From: Matthew Wilcox <willy@infradead.org>
To: Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
dm-devel@redhat.com
Subject: Re: [dm-devel] Sleeping function called from invalid context
Date: Tue, 26 Sep 2023 23:53:33 +0100 [thread overview]
Message-ID: <ZRNg7ctL4cx75RVh@casper.infradead.org> (raw)
In-Reply-To: <ZRNWRyc7xPY17fvt@casper.infradead.org>
On Tue, Sep 26, 2023 at 11:08:07PM +0100, Matthew Wilcox wrote:
> Got this in linux-next 20230926, and I don't think it's due to my
> patches on top (it may be, will verify):
Confirmed not my patches;
git bisect start
# status: waiting for both good and bad commits
# good: [6465e260f48790807eef06b583b38ca9789b6072] Linux 6.6-rc3
git bisect good 6465e260f48790807eef06b583b38ca9789b6072
# status: waiting for bad commit, 1 good commit known
# bad: [4ae73bba62a367f2314f6ce69e3085a941983d8b] Add linux-next specific files for 20230926
git bisect bad 4ae73bba62a367f2314f6ce69e3085a941983d8b
# good: [cc2f2a99c4be7c44a3441dd8f4b9e475d30800c3] Merge branch 'for-next' of https://evilpiepirate.org/git/bcachefs.git
git bisect good cc2f2a99c4be7c44a3441dd8f4b9e475d30800c3
# good: [5a3bc5b9e4e9744f372692a88fd70750ee4851b3] Merge branch 'for-linux-next' of git://anongit.freedesktop.org/drm/drm-misc
git bisect good 5a3bc5b9e4e9744f372692a88fd70750ee4851b3
I'm going to sleep now instead of running the last 10 steps of the
bisect. If nobody's found this when I wake up, I'll finish it then.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2023-09-26 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 22:08 [dm-devel] Sleeping function called from invalid context Matthew Wilcox
2023-09-26 22:53 ` Matthew Wilcox [this message]
2023-09-27 4:42 ` Matthew Wilcox
2023-09-27 15:57 ` Mike Snitzer
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=ZRNg7ctL4cx75RVh@casper.infradead.org \
--to=willy@infradead.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=snitzer@kernel.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