On Mon, 2024-01-22 at 23:42 +0100, Xose Vazquez Perez wrote:
> spotted by indent:
> ./kpartx/gpt.c:623: Warning:old style assignment ambiguity in "=-".
> Assuming "= -"
>
> Cc: Martin Wilck
> Cc: Benjamin Marzinski
> Cc: Christophe Varoqui
> Cc: DM-DEVEL ML
> Signed-off-by: Xose Vazquez Perez
On Mon, Jan 22, 2024 at 05:30:07PM +0100, Mikulas Patocka wrote:
> Hi
>
>
> On Fri, 19 Jan 2024, Ming Lei wrote:
>
> > Hi Mikulas,
> >
> > On Thu, Aug 10, 2023 at 12:07:07PM +0200, Mikulas Patocka wrote:
> > > Hi
> > >
> > > Here I'm submitting the ramdisk discard patches for the next merge
On Mon, Jan 22, 2024 at 05:34:54PM +0100, Mikulas Patocka wrote:
This test always hangs for me as well. You can try this for a reproducer
Create a F39 Cloud image VM on a host machine (tweaking the root-ssh-key
if necessary):
# wget
In an effort to separate intentional arithmetic wrap-around from
unexpected wrap-around, we need to refactor places that depend on this
kind of math. One of the most common code patterns of this is:
VAR + value < VAR
Notably, this is considered "undefined behavior" for signed and pointer
spotted by indent:
./kpartx/gpt.c:623: Warning:old style assignment ambiguity in "=-". Assuming "=
-"
Cc: Martin Wilck
Cc: Benjamin Marzinski
Cc: Christophe Varoqui
Cc: DM-DEVEL ML
Signed-off-by: Xose Vazquez Perez
---
kpartx/gpt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Thu, 18 Jan 2024, Song Liu wrote:
> > Hmm, that's strange - I get a hang with this stacktrace sometimes
> > instantly, sometimes in 30 seconds. I test it on the current kernel from
> > Linus' git - 052d534373b7ed33712a63d5e17b2b6cdbce84fd.
>
> It works for me. I guess there is some
Hi
On Fri, 19 Jan 2024, Ming Lei wrote:
> Hi Mikulas,
>
> On Thu, Aug 10, 2023 at 12:07:07PM +0200, Mikulas Patocka wrote:
> > Hi
> >
> > Here I'm submitting the ramdisk discard patches for the next merge window.
> > If you want to make some more changes, please let me now.
>
> brd discard
Hi,
在 2024/01/20 18:37, Yu Kuai 写道:
The root cause is still not clear yet, however, let's convert dm-raid
back to use md_reap_sync_thread() directly. This is not safe but at
least there won't be new regressions. We can decide what to do after
figuring out the root cause.
I think I finally
On Mon, Jan 22, 2024 at 12:24 AM Yu Kuai wrote:
>
> Hi,
>
> 在 2024/01/21 12:41, Song Liu 写道:
> > On Sat, Jan 20, 2024 at 2:41 AM Yu Kuai wrote:
> >>
> >> From: Yu Kuai
> >>
> >> There are some problems that we fixed in md/raid, and some apis is changed.
> >> However, dm-raid rely the old
Hi,
在 2024/01/21 12:41, Song Liu 写道:
On Sat, Jan 20, 2024 at 2:41 AM Yu Kuai wrote:
From: Yu Kuai
There are some problems that we fixed in md/raid, and some apis is changed.
However, dm-raid rely the old apis(noted that old apis is problematic in
corner cases), and now there are
10 matches
Mail list logo
